SEOking

Website audit report

mozilla.org

76
/ 100
C · Needs work

2 critical and 4 high-severity issues found across 127 checks.

Checks run
127
Passed
87
Failed
30
Pages crawled
12

Scanned 2026-08-17T21:28:46+00:00 · 2 host IPs · cert expires in 64 days

This report is not offered to search engines. It is reachable by link only. If you own mozilla.org you can publish or delete it.

How you compare

Measured against every site SEOking has audited: a corpus that grows with each scan and cannot be reconstructed after the fact.

Your position

64th percentile of 28 sites audited. The average site scores 72, the median 67.

The most unusual thing you fail

JavaScript does not rewrite indexing directives

100% of the sites we have audited get this right and yours does not. Of everything on this report, it is the fault that most sets you apart from your competition, which makes it the first thing worth fixing.

Inbox Trust Index

Our own measure of whether your domain is trusted by the systems that decide if mail reaches an inbox. No other website audit reports this. It is built from BounceZero's deliverability platform.

93
/ 100
Excellent

Your domain is configured the way the top tier of senders are.

Measured against our corpus

We have measured deliverability across 210,156 domains. Yours is not among them, which simply means no one has needed to verify an address at it. The score above is from live measurements of your own DNS.

For context, 2.2% of the domains we have measured accept mail to any address, which makes their bounce behaviour unpredictable.

How your page actually renders

Loaded in a real browser at phone size. This is close to what a visitor and Google's renderer see.

Screenshot of mozilla.org on a mobile viewport
390 × 844 viewport
Largest paint
1.5s
Layout shift
0
Requests
45
Words rendered
1605
JS errors
0
Failed resources
0

Your plan

The 30 faults on this report come from 15 underlying causes. Fixing a cause fixes everything under it, so this is ordered by score returned per unit of work, not by severity alone.

The 7 quickest steps here take you from 76 to about 84. That is 8 points for changes measured in minutes and hours, not weeks.

  1. 1. Repair the language annotations

    Server or CDN config · under an hour→ 79/100

    Translated pages that are not correctly linked to each other are not treated as translations. They compete with each other for the same rankings, and visitors are shown the wrong language.

    Fixes 2 findings: Language links point both ways · Each page lists itself

  2. 2. Stop JavaScript overriding the indexing directives

    Development work · days to weeks→ 83/100

    A canonical or noindex injected at runtime silently overrides what the server said, and the served HTML still looks correct to anyone reading the source.

    Fixes 3 findings: JavaScript does not rewrite indexing directives · Content is readable without running JavaScript · The title survives rendering

  3. 3. Remaining individual fixes

    Mixed · varies→ 86/100

    These do not share a root cause with anything else on the report.

    Fixes 4 findings: Title is the same before and after JavaScript · Pages carry more than their template · Pages deliver what their titles promise · The writing is readable

  4. 4. Fix what search engines are allowed to see

    Server or CDN config · under an hour→ 88/100

    These decide whether your pages can appear at all. Nothing else on this report matters until they are right.

    Fixes 2 findings: XML sitemap published · Homepage canonical is correct

  5. 5. Close the takeover and impersonation gaps

    DNS edit · minutes→ 89/100

    A subdomain pointing at a service that released it can be claimed by anyone, who then publishes on your domain. Deleting the record costs nothing and closes it immediately.

    Fixes 1 finding: No lookalike domain can send mail as your brand

  6. 6. Write the titles and descriptions

    Content work · days→ 92/100

    Your title and description are the advert Google runs for you, free, every time someone searches.

    Fixes 4 findings: Page titles are unique · Meta descriptions are unique · Structured data present · One H1 per page

  7. 7. Make the structured data qualify

    Template change · a few hours→ 94/100

    Rich results — ratings, prices, FAQs, breadcrumbs — are what turn a listing into an advert, and they are decided by whether a few required properties are present. Markup that is invalid or incomplete is work already done that currently earns nothing.

    Fixes 3 findings: The business is identified in structured data · Breadcrumbs are marked up · Site-wide search is declared

  8. 8. Point the site's own authority at the pages that earn

    Template change · a few hours→ 96/100

    Internal links decide which of your pages search engines treat as important, and the decision is usually an accident of navigation design. It costs nothing to change and it changes what ranks.

    Fixes 3 findings: Every page is linked from another · Each page covers a distinct subject · Internal authority is spread, not pooled

  9. 9. Fix email authentication

    DNS edit · minutes→ 97/100

    These are all records in your DNS. One editing session fixes every one of them, and it is the change most likely to stop your mail being filtered.

    Fixes 2 findings: MTA-STS policy published · TLS reporting enabled

  10. 10. Fix the page on a phone

    Template change · a few hours→ 98/100

    Google indexes the mobile version of your site, and these are measured in a real phone-sized browser rather than inferred. A page that scrolls sideways or needs pinching to read loses the visitor before the content matters.

    Fixes 1 finding: Tap targets are big enough to hit

  11. 11. Tidy the URL structure

    Server or CDN config · under an hour→ 98/100

    Depth decides how much authority reaches a page and how often it is recrawled; parameters and capitals manufacture duplicate URLs that compete with the originals.

    Fixes 1 finding: URLs are readable

  12. 12. Decide whether AI assistants may cite you

    Server or CDN config · under an hour→ 99/100

    A growing share of questions are answered without a results page. Being quotable is a distribution channel, and it is usually blocked by a plugin default rather than a decision.

    Fixes 1 finding: A curated summary is published for assistants

  13. 13. Show who stands behind the content

    Content work · days→ 99/100

    Google's guidance asks who produced a page and why they should be trusted. For advice, health, legal or financial topics an anonymous, undated page competes badly against a named one.

    Fixes 1 finding: A publisher is declared in structured data

  14. 14. Harden DNS and hosting

    Server or CDN config · under an hour→ 99/100

    Resilience and reputation work — lower urgency, but cheap while you are already in these systems.

    Fixes 1 finding: DNSSEC enabled

  15. 15. Serve images at the right size and format

    Development work · days to weeks→ 100/100

    Images are what Largest Contentful Paint usually measures, and WebP is typically a third smaller than the same JPEG. On image-led pages this is the largest saving available.

    Fixes 1 finding: Images are sized for the device

Fix these first

Ranked by severity, then by how much score each returns.

  1. critical

    1. Language links point both ways

    +9 pts

    17 hreflang reference(s) are not returned. Page A names page B as its translation, but B does not name A back. Google requires the reference to be mutual and discards the entire set when it is not — so the translations compete with each other instead of being recognised as versions of one page. This is the most common hreflang fault and it fails silently.

    https://www.mozilla.org/
       → names https://www.mozilla.org/en-US/, which does not name it back
    https://www.mozilla.org/ast/
       → names https://www.mozilla.org/ar/, which does not name it back
    https://www.mozilla.org/ast/
       → names https://www.mozilla.org/be/, which does not name it back
    https://www.mozilla.org/ast/
       → names https://www.mozilla.org/bg/, which does not name it back
    3 affected URLs

    How to fix: Every page in a language set must list every other page in that set, including itself. The simplest correct implementation emits the same block of links on all of them.

  2. critical

    2. JavaScript does not rewrite indexing directives

    +9 pts

    JavaScript changes the directives Google acts on after the page loads. The served HTML looks correct to anyone reading the source, and Google indexes what rendering produced — so a canonical or noindex injected at runtime silently overrides everything the server said.

    canonical is added only by JavaScript ('https://www.mozilla.org/en-US/')

    How to fix: Emit the final canonical and robots directives server-side. Nothing that decides indexing should depend on a script running.

  3. high

    3. No lookalike domain can send mail as your brand

    +8 pts

    We generated and checked 55 plausible misspellings and variants of your domain. 6 of the 13 registered variants has mail servers configured, so it is technically able to send email that reads as yours to anyone skimming a sender address. Many such domains are entirely unrelated businesses that happen to have a similar name — this is a risk to be aware of and to defend against, not evidence that anyone is doing anything.

    mozill.org   [mail configured]
    mozilla.online   [mail configured]
    mozilla.shop   [mail configured]
    mozillla.org   [mail configured]
    nozilla.org   [mail configured]
    ozilla.org   [mail configured]
    m0zilla.org
    mizilla.org
    (1 further variant(s) resolve to your own infrastructure and are excluded — those are yours.)

    How to fix: Publish DMARC at enforcement so mail claiming to be your domain is rejected outright — that is the defence that works regardless of who owns a lookalike. Then register the closest unregistered variants; they cost a few pounds a year and are the cheapest brand protection available.

  4. high

    4. Page titles are unique

    +6 pts

    3 pages share 1 duplicated title(s). Google treats near-identical pages as competing with each other, and usually indexes only one.

    3× Mozilla - Internet for people, not profit (US)
    3 affected URLs

    How to fix: Give every page a title describing that page specifically.

  5. high

    5. Each page lists itself

    +6 pts

    2 page(s) declare hreflang for their translations but do not list themselves. A set without a self-reference is ignored, so none of the annotations on those pages currently does anything.

    https://www.mozilla.org/ast/
    https://www.mozilla.org/cak/
    2 affected URLs

    How to fix: Include a self-referencing hreflang on every page in the set.

Full results

Security & trust

Whether the connection, certificate and headers hold up.

10 passed · 0 failed
100%
  • Served over HTTPS

    Secure connection working.

  • HTTP redirects to HTTPS

    Plain HTTP requests are redirected to the secure version.

  • No insecure mixed content

    All resources load securely.

  • Certificate is not near expiry

    Certificate valid for another 64 days (expires 2026-10-21).

  • Modern TLS version

    Negotiated TLSv1.3.

  • HSTS header

    HSTS is set.

  • Content Security Policy header

    Content Security Policy is set.

  • MIME sniffing protection header

    MIME sniffing protection is set.

  • Clickjacking protection header

    Clickjacking protection is set.

  • Referrer policy header

    Referrer policy is set.

Email deliverability

Whether your mail reaches inboxes or spam folders.

8 passed · 2 failed
94%
  • MTA-STS policy publishedlow

    No MTA-STS policy, so mail to you can be delivered unencrypted if an attacker strips TLS.

    Publish an MTA-STS policy and the _mta-sts TXT record.

  • TLS reporting enabledlow

    No TLS-RPT record, so delivery-encryption failures go unreported.

    Publish a _smtp._tls TXT record with a reporting address.

  • DKIM signing is configured

    DKIM keys published on selector(s): google.

  • Domain can receive email

    4 mail server(s) configured.

  • SPF ends with a fail qualifier

    Ends in ~all (soft fail) — the usual safe setting.

  • SPF stays under the lookup limit

    The record forces about 4 DNS lookups. Comfortably within the limit of 10.

  • DMARC reports are collected

    Aggregate reports are being sent to a reporting address.

  • Exactly one SPF record

    One SPF record, as required.

  • DMARC policy is enforced

    DMARC policy is p=reject.

  • BIMI logo published

    BIMI record present — your logo can appear beside your emails.

Speed & Core Web Vitals

How fast real visitors experience the site.

8 passed · 1 failed · 1 skipped
92%
  • Images are sized for the devicelow

    53 of 236 image(s) provide a srcset. Without one, a phone downloads the full desktop image and then scales it down — paying for pixels it never shows.

    Add srcset and sizes so each device downloads an appropriate image.

  • Core Web Vitals from real users

    Not available: PageSpeed API returned 429. This usually means the site does not yet have enough Chrome traffic for Google to report field data. Lab measurements below still apply.

  • Compression enabled

    Served with gzip compression.

  • Server responds quickly

    Median response across 12 page(s) was 514 ms.

  • Homepage HTML is not oversized

    Homepage HTML is 47 KB.

  • Images declare width and height

    12 of 12 images declare dimensions.

  • Reasonable number of scripts

    12 external script file(s) on the homepage.

  • Browser caching is allowed

    Pages may be cached by browsers and CDNs.

  • Images use a modern format

    All 84 image(s) are JPEG or PNG, with no WebP or AVIF alternative. WebP is typically 25-35% smaller at the same quality and is supported by every current browser — on image-led pages this is usually the single largest saving available, and images are what Largest Contentful Paint measures.

  • Images load lazily

    10 of 12 images use lazy loading.

Search fundamentals

The tags, files and signals search engines read first.

22 passed · 11 failed · 2 skipped
71%
  • Language links point both wayscritical

    17 hreflang reference(s) are not returned. Page A names page B as its translation, but B does not name A back. Google requires the reference to be mutual and discards the entire set when it is not — so the translations compete with each other instead of being recognised as versions of one page. This is the most common hreflang fault and it fails silently.

    https://www.mozilla.org/
       → names https://www.mozilla.org/en-US/, which does not name it back
    https://www.mozilla.org/ast/
       → names https://www.mozilla.org/ar/, which does not name it back
    https://www.mozilla.org/ast/
       → names https://www.mozilla.org/be/, which does not name it back
    https://www.mozilla.org/ast/
       → names https://www.mozilla.org/bg/, which does not name it back
    3 affected URLs

    Every page in a language set must list every other page in that set, including itself. The simplest correct implementation emits the same block of links on all of them.

  • Each page lists itselfhigh

    2 page(s) declare hreflang for their translations but do not list themselves. A set without a self-reference is ignored, so none of the annotations on those pages currently does anything.

    https://www.mozilla.org/ast/
    https://www.mozilla.org/cak/
    2 affected URLs

    Include a self-referencing hreflang on every page in the set.

  • Content is readable without running JavaScripthigh

    The served HTML carries 324 words against 1,605 after JavaScript runs. Search engines render pages eventually; assistant crawlers generally do not — they fetch the HTML and read what is there. A page whose content only appears after scripts run is close to empty to them, so it cannot be quoted or cited however good the content is.

    served 324 words → rendered 1,605

    Render the main content server-side. This is the same fix as the js_content finding and it pays twice.

  • XML sitemap publishedmedium

    No XML sitemap. Google has to discover your pages by following links, which means deeper pages may never be crawled.

    0 URLs · not referenced in robots.txt

    Publish sitemap.xml and reference it from robots.txt.

  • The business is identified in structured datamedium

    No Organization markup. This is what Google assembles a knowledge panel from — the box with your logo, name and links that appears beside branded searches — and what connects your site to your social profiles. Without it Google infers your identity from third parties instead of from you.

    Add Organization JSON-LD with name, url, logo and sameAs links to your social profiles.

  • Homepage canonical is correctmedium

    No canonical tag, so duplicate URLs of the same page can compete.

    Set a self-referencing canonical on every page.

  • Structured data presentmedium

    No structured data. Google is reading your page as plain text and cannot qualify you for any rich result.

    Add JSON-LD for Organization and your primary content type.

  • Breadcrumbs are marked upmedium

    No BreadcrumbList markup. Google replaces the raw URL in your listing with a readable breadcrumb trail when this is present, which is more legible and measurably more clickable — and it is one of the cheapest rich results to earn.

    Add BreadcrumbList JSON-LD to every page below the homepage.

  • URLs are readablelow

    3 URL(s) contain capitals, spaces, underscores or a file extension. Google treats /Page and /page as different URLs, so capitals invite duplicates, and underscores are not read as word separators the way hyphens are.

    https://www.mozilla.org/en-US/
    https://www.mozilla.org/en-US/
    https://www.mozilla.org/en-US/
    3 affected URLs

    Use lowercase words separated by hyphens, with no file extension. Redirect the old URLs to the new ones.

  • Site-wide search is declaredlow

    No WebSite markup. With a SearchAction it can give you a search box directly inside your Google listing for branded queries.

    Add WebSite JSON-LD, with potentialAction/SearchAction if the site has its own search.

  • A curated summary is published for assistantslow

    No /llms.txt. It is a short, plain-text map of what a site is and which pages matter — a convention some assistants read to decide what to quote, and cheap to publish. It is not yet a standard anyone is obliged to honour, so treat it as a low-cost bet rather than a requirement.

    Publish /llms.txt: a heading, one paragraph describing the business, and a linked list of your most important pages.

  • Search Console connected

    Not measured — not configured on this instance. Connecting Search Console adds what no crawl can see: the queries this site already appears for, where it ranks, and how many people click. It is read-only and can be disconnected at any time.

  • Current search visibility

    Not measured — ranking data is not configured on this instance.

  • Homepage is indexable

    Homepage is open to indexing.

  • Mobile viewport declared

    Mobile viewport is declared.

  • Homepage title is present and well sized

    Title is 48 characters.

  • Homepage meta description is present

    Description is 134 characters.

  • robots.txt does not block the site

    robots.txt present and open to search engines.

  • Canonicals point at indexable pages

    Every canonical points at a page that is allowed to be indexed.

  • Canonical targets are live pages

    Canonical targets all return 200.

  • Structured data parses

    All structured data blocks are valid JSON.

  • Noindex directives are readable

    No page relies on a directive Google is blocked from reading.

  • Language codes are valid

    Every hreflang value is a valid language or language-region code.

  • Marked-up content qualifies for rich results

    Every marked-up entity carries the properties Google requires.

  • Most crawled pages are indexable

    10 of 10 crawled page(s) (100%) can actually be indexed.

  • Language links point at indexable pages

    Every hreflang target is a live, indexable page.

  • No canonical chains

    No canonical points at a page that then canonicals somewhere else.

  • AI assistants can cite this site

    Every major assistant is allowed to read and cite these pages.

  • Pages are close to the homepage

    Every crawled page sits within four levels of the homepage (deepest: 1).

  • Social preview configured

    7 Open Graph tags found.

  • A default version is declared

    An x-default version is declared for visitors whose language matches none of your versions.

  • Content is not served behind query parameters

    0 of 12 crawled URLs carry query parameters other than tracking tags.

  • Page language declared

    Language attribute present.

  • Link previews are configured for X/Twitter

    3 twitter: tag(s) found.

  • Model-training access is stated

    No model-training crawler is blocked, so this content may be used to train future models. This is a business decision rather than an SEO one, and it is separate from being cited in answers: refusing training does not remove you from AI results, and allowing it does not put you in them.

Content & structure

Whether pages are unique, linked and crawlable.

17 passed · 10 failed · 1 skipped
61%
  • Page titles are uniquehigh

    3 pages share 1 duplicated title(s). Google treats near-identical pages as competing with each other, and usually indexes only one.

    3× Mozilla - Internet for people, not profit (US)
    3 affected URLs

    Give every page a title describing that page specifically.

  • Pages carry more than their templatemedium

    Across 10 page(s), the median page is 65% its own content and the rest navigation, footer and legal text. 3 page(s) carry under 120 words of their own, or less than a third. A word count that includes the template hides this — those pages look substantial and read as empty, which is what a search engine comparing them to a competitor sees.

       76 own /   260 total (29%)  https://www.mozilla.org/be/
       69 own /   211 total (33%)  https://www.mozilla.org/ar/
       98 own /   296 total (33%)  https://www.mozilla.org/
      812 own /  1259 total (64%)  https://www.mozilla.org/ast/
      960 own /  1479 total (65%)  https://www.mozilla.org/en-US/
      913 own /  1402 total (65%)  https://www.mozilla.org/ca/
    3 affected URLs

    Add substance to the page body rather than the template — for product pages, specifics nobody else has; for category pages, an explanation of what the category is for.

  • Each page covers a distinct subjectmedium

    6 pair(s) of pages appear to cover the same subject, judged from their titles and headings. Two pages competing for one query split the links and relevance that should accumulate on one, and Google alternates between them — so neither settles into a stable position. Confirm against Search Console, which shows exactly which page it chooses.

    Mozilla - Internet for people, not profit (US)
       https://www.mozilla.org/en-US/
       https://www.mozilla.org/en-US/
    Mozilla - Internet for people, not profit (US)
       https://www.mozilla.org/en-US/
       https://www.mozilla.org/en-US/
    Mozilla - Internet for people, not profit (US)
       https://www.mozilla.org/en-US/
       https://www.mozilla.org/en-US/
    Internet for people, not profit — Mozilla Global
       https://www.mozilla.org/
       https://www.mozilla.org/en-US/
    6 affected URLs

    Decide which page owns the subject. Merge the weaker one into it and redirect, or narrow each to a genuinely different question.

  • Pages deliver what their titles promisemedium

    2 page(s) have a title and heading whose subject barely appears in the body. Either the title is written for a query the page does not answer — which loses the visitor on arrival and is measurable as a bounce — or the page is about something its title does not say.

    20% of the title's subject in the body
       Internet for people, not profit — Mozilla Global
       https://www.mozilla.org/
    29% of the title's subject in the body
       Internet pa la xente, non pal porgüeyu — Mozilla
       https://www.mozilla.org/ast/
    2 affected URLs

    Make the opening paragraph answer the title directly, or change the title to what the page is really about.

  • Meta descriptions are uniquemedium

    3 pages share 1 duplicated meta description(s). A description is the advert for that specific page; repeating one across a site means Google usually discards it and writes its own from the page text, so you lose control of what searchers read before deciding whether to click.

    We’re working to put control of the internet back in the hands of the people using it.…
       used on 3 pages
    3 affected URLs

    Write one description per page, describing what is on that page.

  • Every page is linked from anothermedium

    1 crawled page(s) are not linked from any other page we fetched. A page reachable only from a sitemap receives no internal authority at all, and is crawled rarely — it can rank, but it starts from nothing and stays there.

    mozilla.org/
    1 affected URL

    Link them from a relevant hub page or from navigation, using the subject as the link text.

  • The writing is readablelow

    Median reading ease is 40.8 — difficult. 3 page(s) score below 40, which is the range of academic and legal writing. That is correct for a terms page and costly on anything meant to sell, because the reader who bounces was the one who arrived.

       8.0 (very difficult)  https://www.mozilla.org/bs/
      25.9 (very difficult)  https://www.mozilla.org/cak/
      33.2 (difficult)  https://www.mozilla.org/ca/
      40.8 (difficult)  https://www.mozilla.org/ast/
      43.8 (difficult)  https://www.mozilla.org/bg/

    Shorter sentences and plainer words in the pages that convert. Legal pages can stay as they are.

  • One H1 per pagelow

    4 of 12 pages do not have exactly one H1 heading.

    4 affected URLs

    Use a single H1 per page stating what the page is about.

  • Internal authority is spread, not pooledlow

    One page receives more than half of all internal links found. That concentrates authority in one place while the rest of the site is starved of it.

    Link deliberately to the pages you want to rank, not only to the same one from every template.

  • A publisher is declared in structured datalow

    No publisher in your structured data. It ties each page back to the organisation that stands behind it, which is what carries trust from your brand to an individual article.

    Add a publisher property naming your Organization, with its logo.

  • Content carries recent dates

    Not measured — no page declares a publication or modification date, so how recently the site was maintained cannot be determined. That is normal for a brochure site and worth fixing for anything article-based.

  • Every page is linked from somewhere

    All 10 crawled pages are reachable by internal links.

  • Pages have enough content

    All 12 crawled pages carry substantial content.

  • Every page has a meta description

    0 of 12 crawled pages have no meta description.

  • Images have alt text

    0 of 236 images across the crawl have no alt attribute. Alt text is how search engines read images and how screen readers describe them.

  • Navigation is present on every page

    Every crawled page carries at least three internal links, so navigation is consistently rendered.

  • Pages are meaningfully different from each other

    No two crawled pages share substantially the same text.

  • No broken internal pages

    All 12 crawled pages returned successfully.

  • Missing pages return a real 404

    No page answers 200 while telling the visitor nothing was found.

  • Navigation promotes pages that earn money

    1 link(s) appear on nearly every page — the site-wide navigation, which is where most internal authority is allocated.

  • Content identifies who wrote it

    Authorship is declared.

  • Links describe where they go

    0 of 1069 internal link(s) use text like 'click here' or no text at all.

  • No phrase is repeated unnaturally

    No phrase dominates a page's text.

  • There is a route to who you are

    An about or contact page is linked.

  • No long redirect chains

    No multi-step redirects found.

  • No dead-end pages

    Every crawled page links onward.

  • Where internal authority goes

    Internal links concentrate authority on the pages below, in order. This is the site's own ranking of itself, derived from how it links — read it against what the business actually sells, because search engines read it the same way. Only the crawled sample is modelled, so this describes the navigation rather than every page.

  • What each page is about

    The terms that distinguish each page from the others on this site — not the most frequent words, but the ones this page uses and the others do not. Read them as what a search engine would take the page to be about, and check that it matches what it is for.

Local business signals

What Google needs to place you in map results.

0 passed · 0 failed · 1 skipped
100%
  • Local business signals

    Not applicable — nothing on this site indicates a physical location customers visit: no address, phone link, opening hours, map or local business markup. Local search checks are skipped and do not affect the score. If you do serve customers from premises, publishing an address and phone number is the place to start.

Infrastructure

DNS, hosting and delivery configuration.

11 passed · 2 failed · 4 skipped
82%
  • No lookalike domain can send mail as your brandhigh

    We generated and checked 55 plausible misspellings and variants of your domain. 6 of the 13 registered variants has mail servers configured, so it is technically able to send email that reads as yours to anyone skimming a sender address. Many such domains are entirely unrelated businesses that happen to have a similar name — this is a risk to be aware of and to defend against, not evidence that anyone is doing anything.

    mozill.org   [mail configured]
    mozilla.online   [mail configured]
    mozilla.shop   [mail configured]
    mozillla.org   [mail configured]
    nozilla.org   [mail configured]
    ozilla.org   [mail configured]
    m0zilla.org
    mizilla.org
    (1 further variant(s) resolve to your own infrastructure and are excluded — those are yours.)

    Publish DMARC at enforcement so mail claiming to be your domain is rejected outright — that is the defence that works regardless of who owns a lookalike. Then register the closest unregistered variants; they cost a few pounds a year and are the cheapest brand protection available.

  • DNSSEC enabledlow

    DNSSEC is not enabled, so DNS answers for your domain can't be cryptographically verified.

    Enable DNSSEC at your DNS provider.

  • Mail server IP is not blacklisted

    Not checked: the blocklists declined queries from this resolver, so reputation could not be confirmed either way. This is excluded from your score rather than guessed at.

  • Certificate history reviewed

    Not measured — the certificate transparency log was unavailable (returned 502).

  • Server log analysis

    Not measured — no log file supplied. Server logs are the only source that shows what Googlebot actually fetched rather than what it could fetch: which pages it spends its crawl on, which it has never asked for, and what it receives when it does.

  • Whole-site analysis

    Not measured — no whole-site crawl has been run for this domain. The audit above reasons from a sample of pages chosen to cover each template, which describes how the site is built. It cannot say how many of the site's pages are indexable, which templates are thin across every instance, or what sits too deep to be crawled — those are counts, and a sample cannot produce one.

  • Redundant nameservers

    4 nameserver(s) configured.

  • No subdomain can be taken over

    Checked 0 subdomain(s); none point at a cloud service that has released them.

  • No unbounded URL spaces

    No filter, session or calendar URLs that would generate an unbounded space were found.

  • Pages are reached without redirect chains

    Every page was reached directly or in a single hop.

  • Crawled URLs return content

    0 of 12 URL(s) followed during this crawl returned a redirect or an error (0%).

  • Certificate is not shared with unrelated domains

    Your certificate covers only your own domain.

  • Internal links pass authority

    0 internal link(s) are marked nofollow.

  • CAA record restricts certificate issuance

    CAA record present.

  • Software versions are not disclosed

    No version numbers advertised in response headers.

  • Hosting network identified

    Served from AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC), announced in 2600:1901::/32 — a block of 79,228,162,514,264,337,593,543,950,336 addresses.

  • What this audit examined

    12 page(s) were examined, chosen to cover 11 of the 80 distinct page templates found across 12 known URLs. Pages are sampled by template rather than in sitemap order, because the first pages of a sitemap are usually all the same kind — a sample of one template would describe that template rather than the site. Findings below therefore apply to the templates listed, and a fault in a template is normally a fault on every page built from it.

Off-page authority

Who links to this site, with what text, and how that compares.

0 passed · 0 failed · 1 skipped
100%
  • Off-page profile

    Not measured — off-page data is not configured on this instance.

What Google's renderer sees

The site loaded in a real browser, the way a visitor and a crawler get it.

11 passed · 4 failed
75%
  • JavaScript does not rewrite indexing directivescritical

    JavaScript changes the directives Google acts on after the page loads. The served HTML looks correct to anyone reading the source, and Google indexes what rendering produced — so a canonical or noindex injected at runtime silently overrides everything the server said.

    canonical is added only by JavaScript ('https://www.mozilla.org/en-US/')

    Emit the final canonical and robots directives server-side. Nothing that decides indexing should depend on a script running.

  • Tap targets are big enough to hitmedium

    51 of 70 tappable element(s) are smaller than 48x48 pixels, and 25 sit closer than 8 pixels to a neighbour. On a phone that means links and buttons that are hard to hit without zooming, and mis-taps on a checkout or contact button cost conversions directly.

    Menu (44x32)
    A (113x36)
    Pause animation (136x32)
    Learn about us (128x22)
    Explore our products (181x22)

    Give tappable elements at least 48x48 CSS pixels and 8 pixels of spacing — usually padding on the link rather than a bigger font.

  • Title is the same before and after JavaScriptmedium

    JavaScript rewrites the page title after load. Google usually indexes the served title, so the one you see in the browser may not be the one shown in search results.

    served:   Internet for people, not profit — Mozilla Global
    rendered: Mozilla - Internet for people, not profit (US)

    Set the final title server-side rather than changing it in script.

  • The title survives renderingmedium

    The title tag changes after JavaScript runs. Google usually indexes the rendered title, but rendering is queued separately and can lag the first crawl, so for a while the served title is what appears in results.

    served:   Internet for people, not profit — Mozilla Global
    rendered: Mozilla - Internet for people, not profit (US)

    Render the final title server-side.

  • Content is in the HTML, not built by JavaScript

    The served HTML contains 324 words and the rendered page 1605 — the content is present before JavaScript runs.

  • The mobile page matches the desktop page

    What the server sends a phone matches what it sends a desktop browser.

  • Largest Contentful Paint under 2.5s (lab)

    Measured 1.5s on a simulated phone viewport. Google's threshold for 'good' is 2.5s.

  • Navigation links are crawlable without JavaScript

    135 links in the served HTML, 89 after rendering — navigation is discoverable.

  • Layout stays stable while loading (lab)

    Cumulative Layout Shift measured at 0.000 (good is 0.1 or less).

  • No JavaScript errors on load

    The page loaded without JavaScript errors.

  • All page resources load successfully

    Every image, script and stylesheet loaded.

  • The page fits the screen

    The page fits the mobile viewport with no sideways scrolling.

  • No excessive JavaScript blocking

    0 long JavaScript task(s) blocked the main thread while loading.

  • Body text is legible on a phone

    0 of 221 text block(s) render below 12px on a mobile viewport.

  • Reasonable number of requests

    The page made 45 network requests to load.

Scan details

Final URLhttps://www.mozilla.org/
Host IPs2600:1901:0:c197::, 35.190.14.201
Pages crawled12 of 12 attempted
Sitemap URLs0
Nameserversns1-240.akam.net, ns4-64.akam.net, ns5-65.akam.net, ns7-66.akam.net
Mail serversalt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx.l.google.com, aspmx3.googlemail.com
DKIM selectorsgoogle
Mail server IPs172.253.157.27, 142.250.102.27, 172.253.116.26
TLSTLSv1.3 · TLS_AES_256_GCM_SHA384 · issued by Google Trust Services
Detected stackcustom / Fastly / other-dns · mail on Google Workspace
Browser renderCamoufox (stealth Firefox) · 5.4s · 1605 words, 89 links after JavaScript
12 URLs crawled
  • https://www.mozilla.org/
  • https://www.mozilla.org/en-US/
  • https://www.mozilla.org/en-US/
  • https://www.mozilla.org/ar/
  • https://www.mozilla.org/ast/
  • https://www.mozilla.org/bg/
  • https://www.mozilla.org/be/
  • https://www.mozilla.org/bs/
  • https://www.mozilla.org/en-US/
  • https://www.mozilla.org/cak/
  • https://www.mozilla.org/ca/
  • https://www.mozilla.org/cs/

Want these fixed?

BounceZero Ltd does this work: technical remediation, local SEO and email deliverability. Tell us what you want fixed and we'll reply with what it takes. No call required, no obligation.

We only email you about this request. No list, no newsletter.

Watch this site

We re-audit on a schedule and email you only when a check that was passing starts failing. That is usually a recent change to the site or its DNS, and it is findable while still fresh. No digest, no newsletter.

Monitoring means repeatedly fetching your site and emailing about it, so we ask you to prove you own mozilla.org first.