SEO report for www.theregister.com
https://www.theregister.com/ · checked Sun, 01 Nov 2026 14:05 GMT
Fix these first
- Render-blocking resourceshigh
2 blocking script(s) and 8 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- Heading structuremedium
375 headings for 7844 words – a lot for the amount of text.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- Anchor text qualitymedium
Same text used for different pages: “systems”, “storage”, “networks”, “hpc”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- HTML sizemedium
980 kB of HTML – heavy for phones (we only analysed the first 1 MB).
Fix: Remove inline bloat, base64 images and unused markup.
- Scripts & third partiesmedium
47 script tag(s); files loaded from 3 other domain(s): fonts.googleapis.com, securepubads.g.doubleclick.net, googletagmanager.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- Imagesmedium
204 image(s).
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- Image alt textmedium
21 of 204 images have no alt attribute.
Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to theregister.com…
Indexing & crawling 100%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✓
XML sitemaphigh
Sitemap index found at https://www.theregister.com/sitemapindex.xml listing 524 sitemaps.
Declared in robots.txt.
Most recent lastmod: 2026-11-01T12:51+01:00.
- ✓
Canonical URLhigh
Canonical: https://www.theregister.com/
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://theregister.com/ → https://www.theregister.com/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
theregister.com redirects to www.theregister.com.
Search snippet & sharing 92%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“Technology news and analysis | The Register”
About 403px of Google's ~580px desktop width.
- ✓
Meta descriptionhigh
88 characters, ~543px of ~990px.
Good length.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en-US"
Content quality 83%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
7,844 words of main content (menus and footer excluded).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- ✓
Readabilitymedium
Flesch reading ease 59 (fairly easy), about 9 words per sentence.
- ✓
Topic focushigh
4 of 4 title keywords appear in the main content.
- ✓
H1 headingcritical
“Technology news and analysis | The Register”
- ✗
Heading structuremedium
375 headings for 7844 words – a lot for the amount of text.
11 skipped level(s), e.g. H2 → H4.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- !
Text-to-code ratiolow
5% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 84%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
Training-only crawlers blocked: GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, CCBot, meta-externalagent. That's a licensing choice – these companies document them as separate from their search crawlers.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- ✓
Question-led contentmedium
9 heading(s) phrased as questions, e.g. “How Google fumbled the frontend with Angular 2”.
- !
Entity clarityhigh
Identified as: Organization.
No sameAs links to official profiles (Google Business Profile, LinkedIn, Facebook, Companies House…).
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✓
Freshness signalsmedium
The page shows when it was published or last updated.
- ✓
Trust pages (E-E-A-T)medium
Links found to all three: about, contact and privacy.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
1 JSON-LD block(s): WebSite, WebPage, Organization, ImageObject, ItemList, ListItem, NewsArticle.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Links 56%
Internal linking, anchor text and broken links.
- !
Internal linkinghigh
487 internal and 31 external links.
Fix: Link to your most important pages from this page with descriptive text.
- ✗
Anchor text qualitymedium
Same text used for different pages: “systems”, “storage”, “networks”, “hpc”.
11 link(s) with no text at all.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- ✓
Broken links (sample)high
No internal links to test.
- !
Internal nofollowlow
5 internal link(s) are nofollow, so search engines may not follow them.
Fix: Remove rel="nofollow" from links to your own pages.
Performance 38%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
146 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- ✗
HTML sizemedium
980 kB of HTML – heavy for phones (we only analysed the first 1 MB).
Fix: Remove inline bloat, base64 images and unused markup.
- ✓
Compressionmedium
Compressed with gzip.
- ✗
Render-blocking resourceshigh
2 blocking script(s) and 8 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
47 script tag(s); files loaded from 3 other domain(s): fonts.googleapis.com, securepubads.g.doubleclick.net, googletagmanager.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
204 image(s).
17 without width/height – can cause layout shift (CLS).
83 image(s) after the first three aren't lazy-loaded.
4 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- ✗
Cachinglow
No Cache-Control header.
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- ✓
HTTP/3low
Server advertises HTTP/3 (faster on mobile networks).
Security 75%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✗
HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- ✗
Security headerslow
Present: none.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 42%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✗
Image alt textmedium
21 of 204 images have no alt attribute.
Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).
- ✗
Form labelsmedium
1 of 3 form field(s) have no label.
Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).
- ✗
Link nameslow
11 link(s) have no readable name for screen readers.
Fix: Add text or aria-label to icon-only links.
- ✗
Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
Local SEO not scored
This site doesn't look like a local business, so these checks are shown for information and not scored.
- i
LocalBusiness markuphigh
No LocalBusiness structured data.
- i
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
- i
Map & directionslow
No map or directions link.