Audit of

www.mozilla.org

https://www.mozilla.org/en-US/

5 findings (0 high, 2 medium, 3 low) · 1179 ms · audited Sat, 26 Sep 2026 23:38:04 GMT

92/100

Excellent

This page is in good shape. Fix the smaller items below and it can hold a top spot.

0 high-impact2 medium3 low21 passed

This page is the report — copy the address from the browser bar to share it, or print it to PDF.

Fix this first

Ranked by impact — each point we deduct is weighted by how much it affects rankings.

XML sitemap

Mediumtechnical

No sitemap found at https://www.mozilla.org/sitemap.xml (HTTP 404).

Why it matters: Without a sitemap, new and updated pages wait for Google to stumble across them, which can take weeks.

Fix: Publish an XML sitemap (most CMSs generate one) and add a Sitemap: line to robots.txt.

Structured data (JSON-LD)

Lowonpage

No JSON-LD structured data on the page.

Why it matters: Structured data is what earns rich results — star ratings, FAQs, opening hours and breadcrumbs in the results list, which lift click-through.

Fix: Add JSON-LD for the page type (Organization, LocalBusiness, Article, FAQPage, Product) and check it in Google's Rich Results Test.

Render-blocking resources

Mediumperformance

5 stylesheet(s) and 3 synchronous script(s) in <head>.

Why it matters: Several blocking files in <head> push first paint out by seconds on a phone, which shows up as a worse LCP score.

Fix: Defer or async the scripts, load non-critical CSS asynchronously, and combine CSS files.

External resources

Lowperformance

1 of 40 referenced resources load from 1 other domain(s).

Why it matters: Every extra domain adds a DNS lookup and connection before the page settles, and third-party scripts can change without warning.

Fix: Keep only the third parties you need, self-host the rest, and preconnect to the domains you keep.

transcend-cdn.com

Score breakdown

The overall score is a weighted average of the four categories (weights shown in brackets).

On-page (weight 35%)

What a searcher and Google see in the listing: title, description, headings, images, mobile.

Technical (weight 30%)

Whether the page can be crawled and indexed, and whether its links work.

Content (weight 20%)

100

How much real, readable content the page carries and how it links internally.

Performance (weight 15%)

Measured-from-HTML signals we could take honestly in one server request.

Every check

26 checks run: 21 passed. Anything we could not verify is marked rather than guessed.

On-page

Page title lengthPass
46 characters: "Mozilla - Internet for people, not profit (US)"
Page title is descriptivePass
The title is unique to this page, not a generic placeholder.
Meta descriptionPass
86 characters: "We’re working to put control of the internet back in the hands of the people using it."
One H1 headingPass
Exactly one H1: "Welcome to Mozilla"
Heading structurePass
44 headings in a clean outline with no skipped levels.
Image alt textPass
All 24 images have an alt attribute (18 marked decorative with alt="").
Canonical tagPass
Canonical present and self-referencing: https://www.mozilla.org/en-US/
Page language declaredPass
<html lang="en">
Mobile viewport tagPass
content="width=device-width, initial-scale=1"
Structured data (JSON-LD)Worth fixinglow
No JSON-LD structured data on the page.
Add JSON-LD for the page type (Organization, LocalBusiness, Article, FAQPage, Product) and check it in Google's Rich Results Test.

Technical

HTTPSPass
The page loads over HTTPS.
Page responds with 200 OKPass
The final response was HTTP 200.
Redirect chainPass
The page loads directly with no redirects.
Indexable (meta robots)Pass
No noindex/nofollow directive in the page HTML.
Indexable (X-Robots-Tag header)Pass
No X-Robots-Tag header blocking indexing.
robots.txtPass
robots.txt found at https://www.mozilla.org/robots.txt, with no sitemap declared.
Page is crawlablePass
robots.txt does not block this page.
XML sitemapWorth fixingmedium
No sitemap found at https://www.mozilla.org/sitemap.xml (HTTP 404).
Publish an XML sitemap (most CMSs generate one) and add a Sitemap: line to robots.txt.
Internal links workPass
Checked 20 internal links; none returned a 404.

Content

Amount of readable contentPass
1547 words of visible text in the HTML.
Text-to-code ratioPass
Visible text is 8.9% of the HTML we received.
Internal linkingPass
31 internal links, 50 external links.

Performance

Server response timePass
267 ms for the server to start sending the page (measured from our server, single request).
HTML page weightWorth fixinglow
114 KB of HTML (does not include images, CSS or JS).
Cut inline scripts and unused template markup, and lazy-load anything below the fold.
Render-blocking resourcesWorth fixingmedium
5 stylesheet(s) and 3 synchronous script(s) in <head>.
Defer or async the scripts, load non-critical CSS asynchronously, and combine CSS files.
External resourcesWorth fixinglow
1 of 40 referenced resources load from 1 other domain(s).
Keep only the third parties you need, self-host the rest, and preconnect to the domains you keep.
- transcend-cdn.com

What we measured

The raw values behind the checks above — useful when somebody asks “how do you know?”.

Title tag: "Mozilla - Internet for people, not profit (US)" (46 chars)
Meta description: "We’re working to put control of the internet back in the hands of the people using it." (86 chars)
H1 / headings: 1 H1 · 24 headings (h2, h2, h2, h2, h2, h2, …)
Images: 24 found · 0 missing alt · 18 decorative (alt="")
Visible words in HTML: 1547
Links: 31 internal · 50 external · checked 20, broken 0, unverified 0
HTTP status / redirects: 200 · 0 redirect(s) from https://www.mozilla.org/en-US/
Final URL: https://www.mozilla.org/en-US/
Canonical: https://www.mozilla.org/en-US/
html lang: en
Viewport: width=device-width, initial-scale=1
Robots directives: meta robots: none · X-Robots-Tag: none
robots.txt: found (HTTP 200) · blocked: no
sitemap: not confirmed (HTTP 404)
Structured data: 0 JSON-LD block(s), 0 valid
Server response time: 267 ms (measured from our server)
HTML size: 113.8 KB
Render-blocking: 5 stylesheet(s) + 3 synchronous script(s) in head
External resources: 1 of 40 referenced assets from transcend-cdn.com

How to read this audit

Every number here comes from the HTML the server returned, its response headers, robots.txt, sitemap.xml and up to 20 internal links — we do not run a browser, so anything the page adds afterwards is invisible to us.
Performance figures are measured from one request from our server, not a Lighthouse or PageSpeed score. Treat them as directional: we can prove a slow server or a bloated document, we cannot prove how fast the page paints for a visitor in another country.