30 Score / 100

F · Critical issues

Page SEO Inspection

https://bluefame.com/

Crawled 29 Sep, 10:08 UTC (2 hr ago)

HTTP 403 5 KB 60 ms TTFB

Download PDF Re-analyze

On-Page Checklist 60% Complete

Primary focus: "noindex" is set via meta robots, so this page will not appear in search results. Fix now →

Full diagnostics

Every check that ran, grouped by what it affects. Problems appear first in each group.

Meta Tags & Search Snippet Simulator

The tags that decide how this page is titled and described in search results.

✕ 1! 10% · needs work

Live snippet simulation

Title width: 147px / 580px

B Bluefame.com bluefame.com

Just a moment...

No meta description, Google will generate a snippet from the page.

Title tag 147px of 580px

The title is only 16 characters; there is room for more descriptive wording (50 to 60 recommended).

Rendered width

Desktop		147px	/ 580px
Mobile		133px	/ 920px

Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 16.

Meta description

The page has no meta description, so search engines will improvise the snippet.

How to fix

<meta name="description" content="A 120 to 160 character summary with a clear call to action.">

Crawling & indexing

Whether search engines can reach, read and index this page at all.

✕ 3! 1i 3✓ 956% · needs work

HTTP status HTTP 403

The page returns HTTP 403 rather than 200.

403 https://www.atom.com/name/BlueFame

How to fix

Restore the page or redirect the URL to a working equivalent.

Robots directives

"noindex" is set via meta robots, so this page will not appear in search results.

meta robots: noindex,nofollow

How to fix

Remove the directive if the page is meant to be found in search.

Robots directives

"nofollow" is set via meta robots.

meta robots: noindex,nofollow

How to fix

Confirm this restriction is intentional.

Canonical tag

No canonical tag, so duplicate URLs may compete with each other.

How to fix

<link rel="canonical" href="https://www.atom.com/name/BlueFame">

Redirect chain 1 redirects

The URL redirects once before resolving, costing an extra round trip.

302 https://bluefame.com/
403 https://www.atom.com/name/BlueFame

How to fix

Link to the final URL directly so visitors and crawlers skip the hop.

Favicon

No favicon is declared. Google shows one beside your result on mobile.

How to fix

<link rel="icon" href="/favicon.svg" type="image/svg+xml">

URL readability

The URL contains uppercase characters, which can produce duplicate URLs for the same page.

/name/BlueFame

How to fix

Serve lowercase URLs and redirect mixed-case variants.

Language

Language is declared as "en-US".

lang="en-US"

hreflang

No hreflang annotations, which is correct for a single-language page.

Viewport

The viewport is configured for mobile.

width=device-width,initial-scale=1

Character encoding

The page declares UTF-8 encoding.

Mixed content

All resources load securely.

URL length 34 characters

The URL is 34 characters.

URL depth 2 levels deep

The page is 2 levels deep.

URL parameters

The URL has no query parameters.

robots.txt 4 KB

robots.txt is present and does not block crawling.

XML sitemap 9 URLs

A sitemap index is published, referencing 9 sitemaps.

Sitemap index referencing 9 sitemaps

Content & metadata

What the page says it is about, and how it reads.

! 2i 2✓ 233% · needs work

Word count 38 Thin content

Headings 0 Little structure

H1 tags 0 None found

Text ratio 1.1% Text vs markup

Heading outline 0 headings

This page has no headings.

Content length 38 words

The page has roughly 38 words, below the ~300 where a page usually reads as substantive.

How to fix

Expand the page to answer the questions a reader arrives with.

Text-to-HTML ratio 1.1% text

Only 1.1% of the page is readable text; the rest is markup and script.

How to fix

Move inline scripts and styles to external files, and remove unused markup.

Open Graph tags

Open Graph tags are incomplete: og:title, og:description, og:image missing.

Open Graph tags

Tag		Status
og:title	✕	Missing
og:description	✕	Missing
og:image	✕	Missing
og:url	✓	Present
og:type	✓	Present

How to fix

<meta property="og:image" content="https://example.com/share-1200x630.jpg">

Twitter card

No twitter:card tag, so shared links render as a small preview.

How to fix

<meta name="twitter:card" content="summary_large_image">

H1 tag

The page has exactly one h1.

www.atom.com

Heading hierarchy

The heading outline descends in order.

Keyword usage

The page has too little text for keyword analysis to mean anything.

AI & answer readiness

Whether answer engines and AI overviews can extract and trust this page.

! 2i 1✓ 457% · fair

AI crawlers 10/10 All allowed

Readable without JS Yes Served complete

Identity , No structured data

Quotable signals 1/4 Schema, date, author, answers

Answer readiness 0 found

No heading is followed by a concise 40 to 60 word answer, the shape featured snippets and AI overviews extract.

How to fix

Open at least one section with a direct 40 to 60 word answer to the question its heading poses.

Content freshness

The page publishes no date in any machine-readable form, so engines cannot tell how current it is.

How to fix

<time datetime="2026-09-17">17 September 2026</time>, or datePublished in Article structured data.

Answer schema

No structured data an answer engine can lift directly, such as FAQPage, HowTo or Article.

How to fix

Mark up question-and-answer content as FAQPage, or step-by-step content as HowTo.

Attribution

Attribution signals present: privacy policy.

Extractable structure

The page is too short to assess structure.

Entity identity

The page has no structured data, so there is no entity to check.

Readable without JavaScript

The page reads the same with and without JavaScript.

llms.txt for AI agents

llms.txt is published, giving AI agents a curated map of the site.

AI crawler access 10 checked

Every AI crawler checked is allowed to read this page.

Speed & delivery

What makes the page slow, and what the loading experience measures.

✕ 3! 3✓ 754% · needs work

Rendered page

The page as it rendered on a mobile viewport during the performance test — **Mobile**, measured

The page as it rendered on a desktop viewport — **Desktop**, measured

LCP Needs work

3.66s

Largest Contentful Paint

Target ≤ 2.5s

58% of real visits are good

What this measures

How long until the largest thing on screen, usually the hero image, video or headline block, has finished rendering. It is a proxy for "when did this page feel loaded".

What moves it: Serve the hero image in a modern format at the size it is displayed, preload it, and remove render-blocking CSS and JavaScript ahead of it. A slow server response delays it too, so check TTFB first.

INP Needs work

384ms

Interaction to Next Paint

Target ≤ 200ms

44% of real visits are good

What this measures

How long the page takes to respond visibly after a tap, click or key press, measured across every interaction, not just the first. High INP is what makes a page feel unresponsive even once it looks ready.

What moves it: Break up long JavaScript tasks so the main thread is free to respond, defer work that is not needed for the interaction, and avoid large re-renders on every event.

CLS Good

0.01

Cumulative Layout Shift

Target ≤ 0.1

92% of real visits are good

What this measures

How much visible content jumps around while the page loads. This is what makes someone tap the wrong thing because a banner or image pushed the layout down underneath their finger.

What moves it: Give images and video explicit width and height so the browser reserves the space, reserve room for ads and embeds, and avoid inserting content above what is already on screen.

FCP Poor

3.04s

First Contentful Paint

Target ≤ 1.8s

53% of real visits are good

What this measures

How long until anything at all appears, the first text or image painted. It separates "the page starts slowly" from "the biggest element is slow": a fast FCP with a slow LCP points at the hero, while both slow points at the server.

What moves it: Cut render-blocking CSS and JavaScript in the head, inline the styles needed for the first screen, and improve the server response time.

TTFB Poor

1849ms

Real-user response time

Target ≤ 800ms

41% of real visits are good

What this measures

How long real visitors waited for the first byte of the response, the 75th percentile across everyone who actually loaded the page, not a single test from one location.

What moves it: Cache the response at the edge, host closer to your visitors, and reduce the work done before the first byte is sent, database queries, template rendering and third-party calls.

Third-party services 23 services · 1.8 MB

23 third-party services account for 81% of what this page downloads, 1.8 MB and 2.0s of main-thread time.

Third-party services

Service	Transferred	Main thread
Google Tag Manager	391 KB	707ms
Intercom	289 KB	294ms
Facebook	257 KB	342ms
Accessibe Accessibility Overlay	237 KB	191ms
termly.io	163 KB	100ms
Other Google APIs/SDKs	107 KB	27ms
Google Fonts	63 KB	,
Pinterest	43 KB	33ms
ID5 Identity Cloud	38 KB	20ms
New Relic	37 KB	31ms
Criteo	32 KB	59ms
openai.com	29 KB	37ms

Showing the 12 heaviest of 23 services.

2.0s of main-thread time

How to fix

Audit what each service earns its weight doing, remove any that duplicate another, and load the rest after the page is interactive.

Browser caching 439 KB re-downloaded

20 files have cache lifetimes short enough that returning visitors download 439 KB again.

Short cache lifetimes

File	Cache lifetime	Size
connect.facebook.net/776488579087398	20m	144 KB
app.termly.io/05e5dfb6-82ce-45e9-8519-ce6070fe3725	4h	141 KB
connect.facebook.net/fbevents.js	20m	113 KB
s.pinimg.com/main.340b6cee.js	14d	38 KB
cdn.id5-sync.com/id5-api.js	1h	35 KB
bzrcdn.openai.com/oaiq.min.js	4h	27 KB
dynamic.criteo.com/ld.js	3h	26 KB
scripts.clarity.ms/clarity.js	1d	25 KB
snap.licdn.com/insight.old.min.js	1d	21 KB
a.quora.com/qevents.js	4h	15 KB
static.cloudflareinsights.com/…6df95cf4e85bb4c19e7a9bdbcba1788362987495	1d	10 KB
app.termly.io/285-7bddfd924baeeae33349.min.js	4h	7 KB

Showing the 12 largest of 20 files.

5 expire within the hour

How to fix

Serve static assets with a long max-age and a content hash in the filename, so a new version gets a new URL rather than a short expiry.

Render-blocking resources 1 found

1 render-blocking resource in the head.

HTML size 5 KB

The HTML document is 5 KB.

Deprecated tags

No deprecated HTML tags are used.

Inline styles 3 found

3 inline style attributes.

Compression

The response is compressed with br.

Content-Encoding: br

Page weight 148 requests · 2.2 MB

The page loads 148 requests totalling 2.2 MB.

What loaded, by type

Type	Requests	Transferred
script	35of 2 declared	1.7 MB
image	43of 1 declared	217 KB
document	3	103 KB
other	63	69 KB
font	1	62 KB
stylesheet	3of 0 declared	19 KB

Of these, 103 requests (1.8 MB) come from third-party domains.

Security

Transport security and the response headers that protect visitors.

i 1✓ 686% · good

Content Security Policy

The Content-Security-Policy allows unsafe-inline or unsafe-eval, which undermines much of its protection.

default-src 'none'; script-src 'nonce-uaOBHRpFCyrlo6vdFWW5M5' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline…

How to fix

Use nonces or hashes instead of unsafe-inline.

HSTS

HTTPS is enforced with Strict-Transport-Security.

max-age=31536000; includeSubDomains; preload

MIME sniffing

MIME sniffing is disabled.

Clickjacking protection

The page is protected against framing.

Referrer policy

Referrer-Policy is "same-origin".

same-origin

Version disclosure

No software versions are disclosed in headers.

TLS certificate 64 days left

The TLS certificate is valid for another 64 days.

64 days remaining

Links, media & schema

Links, images and structured data.

! 2✓ 982% · good

Social share preview From this page's Open Graph tags

Structured data

The page has no structured data, so it cannot qualify for rich results.

How to fix

<script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","headline":"…"}</script>

Image dimensions 1 found

1 image has no width and height, so the page shifts as they load (hurting CLS).

# / line	Image source
JS	/favicon.ico`<img src="/favicon.ico" class="AqZx3" alt="Icon for www.atom.com">`

How to fix

<img src="…" width="800" height="600">, the browser reserves the space before decoding.

Link distribution 2 resources

0 internal and 2 external links.

0 internal, 2 external

0 internal, 2 external

Anchor text

Anchor text describes its destinations.

Link rel attributes

Outbound link rel attributes look appropriate.

In-page anchors

In-page anchors resolve to real targets.

Image alt text

All images carry an alt attribute.

Image formats

No heavy legacy image formats found.

Image loading

Image loading strategy looks sound.

Responsive images

Images are served responsively or are small enough not to need it.

Broken links 2 checked

All 2 checked links resolve.

What to fix first

Ranked by impact against effort, the top of this list buys the most for the least work.

✕ Critical "noindex" is set via meta robots, so this page will not appear in search results.

Remove the directive if the page is meant to be found in search.

quick fix

✕ Critical The page returns HTTP 403 rather than 200.

Restore the page or redirect the URL to a working equivalent.

moderate

✕ Critical Real users wait 1849ms for the first byte, above the 800ms target.

Cache at the edge, move hosting closer to visitors, or cut server work before the first byte.

moderate

! Recommended The page has no meta description, so search engines will improvise the snippet.

quick fix

! Recommended 1 image has no width and height, so the page shifts as they load (hurting CLS).

<img src="…" width="800" height="600">, the browser reserves the space before decoding.

quick fix

! Recommended Largest Contentful Paint is 3.7s (real-user data), above the 2.5s target.

Optimise the hero image, remove render-blocking CSS and JS, and improve server response time.

moderate

! Recommended 23 third-party services account for 81% of what this page downloads, 1.8 MB and 2.0s of main-thread time.

Audit what each service earns its weight doing, remove any that duplicate another, and load the rest after the page is interactive.

moderate

! Recommended "nofollow" is set via meta robots.

Confirm this restriction is intentional.

quick fix

! Recommended No canonical tag, so duplicate URLs may compete with each other.

quick fix

! Recommended The page publishes no date in any machine-readable form, so engines cannot tell how current it is.

<time datetime="2026-09-17">17 September 2026</time>, or datePublished in Article structured data.

quick fix

! Recommended The page has no structured data, so it cannot qualify for rich results.

quick fix

! Recommended 20 files have cache lifetimes short enough that returning visitors download 439 KB again.

Serve static assets with a long max-age and a content hash in the filename, so a new version gets a new URL rather than a short expiry.

quick fix

Score breakdown

How each area scored. Categories that could not be measured are excluded rather than counted as zero.

Indexability & Crawling24 checks · 8 issues

On-Page Content & Structure14 checks · 9 issues

Core Web Vitals13 checks · 6 issues

Schema & Rich Snippets1 checks · 1 issue

Media & Links10 checks · 1 issue

Overall scoreGrade F · 37/66 passed