RankAgent logoRankAgentAudit another site

SEO audit report

pinkseo.marketing: homepage SEO audit

Audited 29 August 2026 · 32 checks · homepage only

SEO score

90

Grade A+

Issues to fix

6

None critical

AI search readiness

6/8

AI-readiness checks passed

Summary

The website is doing really well overall, but the main thing holding you back is your mobile experience—while your site works on phones, it could feel smoother and more responsive. The good news is that your content is excellent and your site is secure, which gives visitors confidence. To make the biggest quick improvement, I'd suggest optimizing those 45 images you're loading—they're slowing things down, and compressing or removing a few could noticeably speed up how fast your pages appear, especially on mobile devices where people are more impatient.

Category scores

Weighted by our audit methodology — our view of what to fix first, not measured Google ranking factors.

MobileB · 70/100
HeadingsA+ · 90/100
Meta TagsA+ · 92/100
PerformanceA+ · 93/100
Content & SEO ReadinessA+ · 96/100
SecurityA+ · 100/100

What to fix (6)

Most important first. Each finding says what was found, why it matters, and how to fix it.

  1. ImportantMeta Tags

    Link previews aren't set up

    When someone shares your page on WhatsApp, Facebook, or LinkedIn, it won't show a proper preview (missing: image). A good preview gets far more clicks than a bare link.

    How to fix: Add og:title, og:description and og:image meta tags in your page header. Most website builders and the Yoast SEO plugin can set these for you.

  2. ImportantPerformance

    This page loads a lot of images (45)

    Many images can slow a page down. Make sure they're compressed and that off-screen images load lazily so visitors aren't waiting.

    How to fix: Compress images, serve modern formats like WebP, and add loading="lazy" to images below the fold.

  3. ImportantMobile

    2 elements have a fixed width

    Some parts of this page use a fixed pixel width wider than 500px. These can spill off the side of a phone screen and force annoying sideways scrolling.

    How to fix: Use flexible widths (%, max-width) instead of fixed pixel widths so content adapts to small screens.

  4. MinorHeadings

    Headings skip levels

    Headings work like a table of contents (H1 → H2 → H3). This page jumps a level somewhere, which makes the structure harder for Google and screen readers to follow.

    How to fix: Use headings in order — don't jump from H2 straight to H4. Pick heading levels for structure, not for font size (use CSS for styling).

  5. MinorContent & SEO Readiness

    No llms.txt file found

    llms.txt is a new, simple file that tells AI assistants like ChatGPT what your business does and which pages matter most — making it easier for them to describe and recommend you accurately. It's optional today, but an easy edge while most sites don't have one.

    How to fix: Add a plain-text /llms.txt at the root of your site summarising your business and linking your key pages. RankAgent can generate one for you.

  6. MinorContent & SEO Readiness

    No author or byline found

    This page doesn't say who wrote it. Google's E-E-A-T guidelines (Experience, Expertise, Authoritativeness, Trust) reward content with a credible, named author — and AI assistants weigh authorship when deciding what to trust and cite.

    How to fix: Add a visible byline and a short author bio with real credentials, and mark it up with author structured data.

Fix this site

This page lists 6 homepage issues. RankAgent audits every page of the site and gives the exact fix for each, in plain language.

Start 14-day free trial

No card required.

Auditing this for a client?

Turn pinkseo.marketing into a print-ready pitch one-pager with your logo and a 30-day plan.

Pitch this to a client →

AI search readiness

Whether ChatGPT, Perplexity and Google's AI answers can read, understand and quote this page. A separate question from Google rankings.

Check if ChatGPT mentions pinkseo.marketing →
  • ✓AI assistants (ChatGPT, Perplexity) can read this site
  • !No llms.txt file found
  • ✓This page uses structured data
  • ✓The question headings have direct answers
  • ✓This page uses question-style headings
  • !No author or byline found
  • ✓This page shows a date
  • ✓This page includes data points

What's working (20)

Checks this homepage passed.

  • ✓The page title is a good length
  • ✓The meta description is a good length
  • ✓This page tells Google which version is the main one
  • ✓This page has exactly one main heading
  • ✓The main heading is a good length
  • ✓This page responded quickly (0.6s)
  • ✓This page's code is a healthy size (92KB)
  • ✓This page loads without a redirect chain
  • ✓Nothing is blocking this page from displaying
  • ✓This page is set up to fit mobile screens
  • ✓This site uses a secure (HTTPS) connection
  • ✓All content loads securely
  • ✓This page has plenty of content (723 words)
  • ✓Most images have descriptions
  • ✓This page links to other pages on the site (57)
  • ✓This site has a favicon
  • ✓This site has a robots.txt file
  • ✓Search engines are allowed to show this page
  • ✓Search engines are allowed to crawl this site
  • ✓This site has a sitemap

Further reading

Send this report to the site owner, or keep the link for later.