Login

Automated Report

WordSegments.com

Generated on September 21, 2025 · Domain: wordsegments.com

Instant Audit

See your site the way search engines feel it

Launch a free crawl in under 30 seconds and get a ranked hit-list of fixes that lift speed, visibility, and trust.

Start Free Analysis
Favicon
WordSegments.com
2025/09/21
54

Overall Score

85

PageSpeed

46

Website Quality

31

Trust & Security

53

Performance

100

SEO

100

Best Practices

83

Accessibility

Performance
53/100
Largest Contentful Paint
0/25
20.2s
2.5s4.0s
First Contentful Paint
0/10
13.6s
1.8s3.0s
Total Blocking Time
28/30
161ms
200ms400ms
Cumulative Layout Shift
25/25
0.00
0.100.25
Speed Index
0/10
13.6s
3.4s5.4s
SEO
100/100
Page isn’t blocked from indexing
40/40
Document has a `<title>` element
10/10
Document has a meta description
10/10
Page has successful HTTP status code
10/10
Links have descriptive text
10/10
Links are crawlable
10/10
Document has a valid `hreflang`
10/10
Best Practices
100/100
Uses HTTPS
18/18
Avoids deprecated APIs
18/18
Avoids third-party cookies
18/18
Allows users to paste into input fields
11/11
Avoids requesting the geolocation permission on page load
4/4
Avoids requesting the notification permission on page load
4/4
Displays images with correct aspect ratio
4/4
Serves images with appropriate resolution
4/4
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
4/4
Document uses legible font sizes
4/4
Page has the HTML doctype
4/4
Properly defines charset
4/4
No browser errors logged to the console
4/4
No issues in the `Issues` panel in Chrome Devtools
4/4
Accessibility
83/100
`[aria-*]` attributes match their roles
6/6
`[aria-hidden="true"]` is not present on the document `<body>`
6/6
`[role]`s have all required `[aria-*]` attributes
6/6
`[aria-*]` attributes have valid values
6/6
`[aria-*]` attributes are valid and not misspelled
6/6
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
6/6
`button`, `link`, and `menuitem` elements do not have accessible names.
0/4
ARIA attributes are used as specified for the element's role
4/4
Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names.
0/4
`[aria-hidden="true"]` elements do not contain focusable descendents
4/4
Elements use only permitted ARIA attributes
4/4
`[role]` values are valid
4/4
Background and foreground colors do not have a sufficient contrast ratio.
0/4
Document has a `<title>` element
4/4
`<html>` element does not have a `[lang]` attribute
0/4
Links have a discernible name
4/4
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
4/4
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
4/4
No element has a `[tabindex]` value greater than 0
4/4
Touch targets have sufficient size and spacing.
4/4
Uses ARIA roles only on compatible elements
1/1
Deprecated ARIA roles were not used
1/1

Site Quality

Title
12/20
WordSegments
12 chars (ideal 30–60)
Meta Description
15/15
WordSegments. Challenge yourself daily and guess a 5-letter word using segments of your previous guessed letters as clues.
122 chars (ideal 120–160)
Favicon
3/3
Favicon preview
https://www.google.com/s2/favicons?domain=wordsegments.com&sz=48
present
Viewport meta
8/8
width=device-width, initial-scale=1
correct (width=device-width, initial-scale=1)
robots.txt
0/6
missing (ideal: User-agent: * + Allow: / + Sitemap)
Sitemap
0/7
missing (create sitemap.xml and submit to Google Search Console)
Headings
0/6
missing (add H1, H2, H3, H4, H5, H6 tags to structure content)
Schema.org JSON-LD
0/2
missing (consider Organization, Article, Product, or FAQPage schemas)
Canonical URL
0/8
missing (add <link rel='canonical'> to avoid duplicate content)
HTML lang
0/4
missing (add lang='en' to <html> tag)
Character encoding
4/4
utf-8
present

Open Graph

Title
0/3
missing (add <meta property='og:title'> for social sharing)
Description
0/3
missing (add <meta property='og:description'> for social sharing)
Image
0/3
missing (add <meta property='og:image'> with 1200x630px image)
URL
0/3
missing (add <meta property='og:url'> with full URL)
Type
0/1
missing (add <meta property='og:type' content='website'>)

Twitter Cards

Card Type
1/1
summary_large_image
present
Title
1/1
WordSegments
present
Description
1/1
Challenge yourself daily and guess a 5-letter word using segments of your previous guessed letters as clues.
present
Image
1/1
Image preview
https://www.wordsegments.com/og-image.png
present

Security Headers

HTTPS
30/30
HTTPS enabled
HTTP Strict Transport Security
0/15
missing (should be: Strict-Transport-Security: max-age=31536000; includeSubDomains)
Content Security Policy
0/15
missing (should be: Content-Security-Policy: default-src 'self')
Frame Protection
0/5
missing (should be: X-Frame-Options: SAMEORIGIN)
MIME Type Protection
0/5
missing (should be: X-Content-Type-Options: nosniff)

Domain Trust

Domain Rating
0/25
no domain rating found
1525
Domain Age
1/5
1 years
Registrar
NAMECHEAP INC
Country
IS

Infrastructure

Provider
no hosting or CDN provider detected

FAQs

Report-specific answers

Key takeaways for WordSegments.com pulled from this audit.

How often should I refresh the YourWebsiteScore report for WordSegments.com?

The latest audit was captured on September 21, 2025.

Re-run the analysis after major deployments or at least once a month so you can spot Core Web Vitals, snippet, or security regressions before they affect rankings or conversions.

Which Lighthouse performance improvements should WordSegments.com tackle first?

Largest Contentful Paint (mobile) at 20.2s: reclaim ≈25 points. Optimise hero media, inline critical CSS, and prioritise above-the-fold requests so the primary content renders faster.

Largest Contentful Paint (desktop) at 3.5s: reclaim ≈19 points. Optimise hero media, inline critical CSS, and prioritise above-the-fold requests so the primary content renders faster.

First Contentful Paint (mobile) at 13.6s: reclaim ≈10 points. Reduce render-blocking CSS/JS and stream initial HTML so meaningful content appears earlier.

Which Lighthouse SEO audits should WordSegments.com fix first?

Mobile Lighthouse SEO is 100/100. Keep schema, robots directives, and headings tidy so the score stays maxed.

Desktop Lighthouse SEO is 100/100. Keep schema, robots directives, and headings tidy so the score stays maxed.

Which Lighthouse Best Practices should WordSegments.com fix first?

Mobile Lighthouse Best Practices score is 100/100. Keep TLS, resource loading, and client-side APIs up-to-date to stay maxed.

Desktop Lighthouse Best Practices score is 100/100. Keep TLS, resource loading, and client-side APIs up-to-date to stay maxed.

Which Lighthouse Accessibility audits should WordSegments.com fix first?

`button`, `link`, and `menuitem` elements do not have accessible names. (mobile) is missing roughly 4 points. Fixing it will raise the Accessibility score and make WordSegments.com easier to use.

Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names. (mobile) is missing roughly 4 points. Fixing it will raise the Accessibility score and make WordSegments.com easier to use.

Background and foreground colors do not have a sufficient contrast ratio. (mobile) is missing roughly 4 points. Fixing it will raise the Accessibility score and make WordSegments.com easier to use.

`button`, `link`, and `menuitem` elements do not have accessible names. (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make WordSegments.com easier to use.

Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names. (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make WordSegments.com easier to use.

Background and foreground colors do not have a sufficient contrast ratio. (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make WordSegments.com easier to use.

Which Website Quality issues should WordSegments.com fix first?

Title: missing ≈8 points. 12 chars (ideal 30–60). Focus on it to lift WordSegments.com's Website Quality score.

Canonical URL: missing ≈8 points. Missing (add <link rel='canonical'> to avoid duplicate content). Focus on it to lift WordSegments.com's Website Quality score.

Sitemap: missing ≈7 points. Missing (create sitemap.xml and submit to Google Search Console). Focus on it to lift WordSegments.com's Website Quality score.

Which Trust & Security fixes should WordSegments.com tackle first?

Domain Rating: missing ≈25 points. No domain rating found. Close this gap to raise WordSegments.com's Trust & Security score.

HTTP Strict Transport Security: missing ≈15 points. Missing (should be: Strict-Transport-Security: max-age=31536000; includeSubDomains). Close this gap to raise WordSegments.com's Trust & Security score.

Content Security Policy: missing ≈15 points. Missing (should be: Content-Security-Policy: default-src 'self'). Close this gap to raise WordSegments.com's Trust & Security score.

Instant Audit

See your site the way search engines feel it

Launch a free crawl in under 30 seconds and get a ranked hit-list of fixes that lift speed, visibility, and trust.

Start Free Analysis