SEOking

Website audit report

novadose.com

84
/ 100
B · Good

23 issues found across 137 checks. Nothing critical.

Checks run
137
Passed
105
Failed
23
Pages crawled
12

Scanned 2026-08-31T23:40:36+00:00 · 4 host IPs · cert expires in 48 days

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

What changed since last time

Clear improvement — 1 check(s) fixed since the last audit. Score +2.

Fixed since last audit

  • Server responds quickly

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

79th percentile of 29 sites audited. The average site scores 72, the median 71.

The most unusual thing you fail

Marked-up content qualifies for rich results

92% 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.

65
/ 100
Fair

Working, but with faults that measurably cost you inbox placement.

What is pulling it down: DMARC enforcement. See the email deliverability section below.

Measured against our corpus

We have measured deliverability across 221,734 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, 3.5% 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 novadose.com on a mobile viewport
390 × 844 viewport
Largest paint
3.5s
Layout shift
0
Requests
52
Words rendered
1555
JS errors
0
Failed resources
4

Score over time

64
66
64
65
83
85
85
85
84
83
82
84

Oldest on the left. Every re-run is kept.

Your plan

The 23 faults on this report come from 12 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 5 quickest steps here take you from 84 to about 90. That is 6 points for changes measured in minutes and hours, not weeks.

  1. 1. Fix email authentication

    DNS edit · minutes→ 86/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 5 findings: DMARC policy is enforced · DMARC reports are collected · MTA-STS policy published · TLS reporting enabled · BIMI logo published

  2. 2. Close the takeover and impersonation gaps

    DNS edit · minutes→ 87/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

  3. 3. Remaining individual fixes

    Mixed · varies→ 89/100

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

    Fixes 3 findings: Pages carry more than their template · The writing is readable · Every submitted page is reachable by a link

  4. 4. Make the structured data qualify

    Template change · a few hours→ 91/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 2 findings: Marked-up content qualifies for rich results · Rendering preserves the structured data

  5. 5. Decide whether AI assistants may cite you

    Server or CDN config · under an hour→ 93/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 2 findings: AI assistants can cite this site · A curated summary is published for assistants

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

    Template change · a few hours→ 94/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 2 findings: Navigation promotes pages that earn money · Each page covers a distinct subject

  7. 7. Harden DNS and hosting

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

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

    Fixes 2 findings: All page resources load successfully · DNSSEC enabled

  8. 8. Fix the page on a phone

    Template change · a few hours→ 97/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 2 findings: Tap targets are big enough to hit · Body text is legible on a phone

  9. 9. Reduce what the page has to load

    Development work · days to weeks→ 98/100

    Image and script weight drive every speed metric you are failing. This is the slowest fix here and the one with the longest tail.

    Fixes 1 finding: Largest Contentful Paint under 2.5s (lab)

  10. 10. Complete the security headers

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

    All set in the same place — your web server or CDN. Half of them are single lines.

    Fixes 1 finding: Content Security Policy header

  11. 11. Write the titles and descriptions

    Content work · days→ 99/100

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

    Fixes 1 finding: Every page has a meta description

  12. 12. 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. high

    1. DMARC policy is enforced

    +9 pts

    DMARC policy is p=none. p=none monitors only — it instructs receivers to do nothing, so nobody is actually prevented from spoofing your domain.

    v=DMARC1; p=none;

    How to fix: Move to p=quarantine, then p=reject, once your reports are clean.

  2. high

    2. Largest Contentful Paint under 2.5s (lab)

    +8 pts

    Measured 3.5s on a simulated phone viewport. Google's threshold for 'good' is 2.5s. This is the metric most likely to be costing you both rankings and visitors who leave before the page paints.

    LCP 3496 ms · FCP 675 ms

    How to fix: Compress and preload the largest above-the-fold image, and cache the HTML at the edge.

  3. high

    3. No lookalike domain can send mail as your brand

    +8 pts

    We generated and checked 60 plausible misspellings and variants of your domain. 1 of the 3 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.

    novadise.com   [mail configured]
    novadoes.com
    novados.com

    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. Marked-up content qualifies for rich results

    +7 pts

    1 required propert(y/ies) are missing from your structured data. The markup exists but does not qualify for the rich result it is aiming at — which is the worst of both: the work has been done and earns nothing in the results page.

    LocalBusiness is missing 'address'

    How to fix: Add the missing properties. Google's Rich Results Test shows exactly which are required for each type.

  5. high

    5. Pages carry more than their template

    +7 pts

    Across 12 page(s), the median page is 35% its own content and the rest navigation, footer and legal text. 7 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. Every page of this type that was checked has this fault, and your sitemap lists 2 pages built from the same template (/shop) — so this is most likely one template fix affecting up to 2 pages, not 1.

       89 own /   722 total (12%)  https://novadose.com/product-category/recovery/
       93 own /   726 total (13%)  https://novadose.com/product-category/pens/
       97 own /   730 total (13%)  https://novadose.com/product-category/longevity/
      101 own /   734 total (14%)  https://novadose.com/shop/
      101 own /   734 total (14%)  https://novadose.com/product-category/cartridges/
      143 own /   795 total (18%)  https://novadose.com/product-category/metabolic/
    7 affected URLs

    How to fix: 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.

Full results

Security & trust

Whether the connection, certificate and headers hold up.

10 passed · 1 failed
93%
  • Content Security Policy headermedium

    Missing. Limits where scripts may load from, which is the main defence against injected code and card skimmers.

    Add a Content-Security-Policy header, starting in report-only mode.

  • 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.

  • Cookies are protected

    Cookies set Secure and HttpOnly.

  • Certificate is not near expiry

    Certificate valid for another 48 days (expires 2026-10-19).

  • Modern TLS version

    Negotiated TLSv1.3.

  • HSTS header

    HSTS 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.

5 passed · 5 failed
69%
  • DMARC policy is enforcedhigh

    DMARC policy is p=none. p=none monitors only — it instructs receivers to do nothing, so nobody is actually prevented from spoofing your domain.

    v=DMARC1; p=none;

    Move to p=quarantine, then p=reject, once your reports are clean.

  • DMARC reports are collectedmedium

    No rua= address, so DMARC failures are generated and then discarded. You have no visibility into who is sending as you.

    v=DMARC1; p=none;

    Add rua=mailto:dmarc@yourdomain to start collecting reports.

  • 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.

  • BIMI logo publishedlow

    No BIMI record. With DMARC at enforcement you could display your logo next to your messages in Gmail and Apple Mail.

    Once DMARC is at quarantine or reject, publish a BIMI record with an SVG logo.

  • DKIM signing is configured

    DKIM keys published on selector(s): google, k2.

  • Domain can receive email

    5 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 1 DNS lookups. Comfortably within the limit of 10.

  • Exactly one SPF record

    One SPF record, as required.

Speed & Core Web Vitals

How fast real visitors experience the site.

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

    0 of 175 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 163 ms.

  • Homepage HTML is not oversized

    Homepage HTML is 328 KB.

  • Images declare width and height

    30 of 35 images declare dimensions.

  • Reasonable number of scripts

    13 external script file(s) on the homepage.

  • Browser caching is allowed

    Pages may be cached by browsers and CDNs.

  • Images use a modern format

    162 image(s) are served as WebP or AVIF.

  • Images load lazily

    35 of 35 images use lazy loading.

Search fundamentals

The tags, files and signals search engines read first.

31 passed · 4 failed · 3 skipped
90%
  • Marked-up content qualifies for rich resultshigh

    1 required propert(y/ies) are missing from your structured data. The markup exists but does not qualify for the rich result it is aiming at — which is the worst of both: the work has been done and earns nothing in the results page.

    LocalBusiness is missing 'address'

    Add the missing properties. Google's Rich Results Test shows exactly which are required for each type.

  • AI assistants can cite this sitemedium

    2 assistant crawler(s) are blocked in robots.txt, so this site cannot be cited in the answers they write: Applebot-Extended, Google-Extended. These are the crawlers that fetch a page in order to reference it in a reply, which is a referral rather than a copy. Blocking them is a legitimate choice — but it is usually a plugin or CDN default rather than a decision anyone made.

    Applebot-Extended — blocks Apple Intelligence
    Google-Extended — blocks Google AI Overviews and Gemini grounding

    If you want to appear in AI answers, allow these agents in robots.txt. If the block is deliberate, no change is needed — but confirm it was deliberate.

  • Rendering preserves the structured datamedium

    1 structured data type(s) present in the served HTML are gone from the rendered page: LocalBusiness. Something on the page is removing or replacing the markup after load, and Google indexes the rendered result.

    LocalBusiness

    Find the script rewriting the head — usually a framework hydration step replacing server-rendered tags.

  • 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.

  • International targeting

    Not applicable — this site publishes in a single language and declares no regional or translated versions, so hreflang annotations are not needed. Adding them to a single-language site does nothing.

  • 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 55 characters.

  • XML sitemap published

    Sitemap found listing 32 URLs.

  • Homepage meta description is present

    Description is 120 characters.

  • Homepage canonical is correct

    Canonical points at this page.

  • Structured data present

    Structured data found: BreadcrumbList, CollectionPage, ImageObject, ListItem, Organization, WebPage, WebSite.

  • robots.txt does not block the site

    robots.txt present and open to search engines. 9 named crawler(s) are blocked, which is a deliberate choice rather than a fault.

  • 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.

  • Sitemap and page directives agree

    No page is both listed in the sitemap and marked noindex.

  • 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.

  • Most crawled pages are indexable

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

  • The business is identified in structured data

    Identified as LocalBusiness, Organization.

  • The business is a describable entity

    Organization or Person markup names the business to assistants.

  • No canonical chains

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

  • Sitemap lists canonical pages only

    Every sitemap URL is its own canonical.

  • Structured data is in the served HTML

    All structured data is present in the HTML the server sends.

  • Content is marked up to be answered

    FAQPage or HowTo markup gives assistants a structured answer to cite.

  • Breadcrumbs are marked up

    BreadcrumbList markup is present.

  • Pages are close to the homepage

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

  • The entity links out to its profiles

    sameAs links the entity to its real profiles across the web.

  • Social preview configured

    10 Open Graph tags found.

  • URLs are readable

    URLs use lowercase, hyphenated, extension-free paths.

  • 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.

  • Site-wide search is declared

    WebSite markup is present.

  • Link previews are configured for X/Twitter

    4 twitter: tag(s) found.

  • Structured data in use

    132 structured data object(s) across 12 page(s): Answer, Brand, BreadcrumbList, CollectionPage, FAQPage, ImageObject, ListItem, LocalBusiness, Offer, Organization, and others.

  • Model-training access is stated

    5 training crawler(s) blocked: Bytespider, CCBot, ClaudeBot, GPTBot, meta-externalagent. 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.

25 passed · 5 failed
80%
  • Pages carry more than their templatehigh

    Across 12 page(s), the median page is 35% its own content and the rest navigation, footer and legal text. 7 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. Every page of this type that was checked has this fault, and your sitemap lists 2 pages built from the same template (/shop) — so this is most likely one template fix affecting up to 2 pages, not 1.

       89 own /   722 total (12%)  https://novadose.com/product-category/recovery/
       93 own /   726 total (13%)  https://novadose.com/product-category/pens/
       97 own /   730 total (13%)  https://novadose.com/product-category/longevity/
      101 own /   734 total (14%)  https://novadose.com/shop/
      101 own /   734 total (14%)  https://novadose.com/product-category/cartridges/
      143 own /   795 total (18%)  https://novadose.com/product-category/metabolic/
    7 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.

  • Navigation promotes pages that earn moneymedium

    12 link(s) appear on nearly every page — the site-wide navigation, which is where most internal authority is allocated. 2 of them point at legal, account or administrative pages, and 1 of those sits among the eight best-linked pages on the site — level with, or above, the pages you sell from. Nobody decides this: a crawler counts every footer link as an endorsement repeated on every page, while visitors ignore footers. Those pages must exist and should not be among the best-linked things you publish.

    novadose.com/  4.0%
    novadose.com/shop  4.0%
    novadose.com/product-category/cartridges  4.0%
    novadose.com/lab-testing  4.0%
    novadose.com/shipping  4.0%
    novadose.com/faq  4.0%
    novadose.com/affiliate-program  4.0%
    novadose.com/contact  4.0%
  • Each page covers a distinct subjectmedium

    4 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. Every page of this type that was checked has this fault, and your sitemap lists 2 pages built from the same template (/shop) — so this is most likely one template fix affecting up to 2 pages, not 1.

    Shop Peptide Pens | NovaDose
       https://novadose.com/shop/
       https://novadose.com/product-category/pens/
    Metabolic Archives - NovaDose
       https://novadose.com/product-category/metabolic/
       https://novadose.com/product-category/longevity/
    Metabolic Archives - NovaDose
       https://novadose.com/product-category/metabolic/
       https://novadose.com/product-category/recovery/
    Longevity Archives - NovaDose
       https://novadose.com/product-category/longevity/
       https://novadose.com/product-category/recovery/
    4 affected URLs

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

  • Every page has a meta descriptionmedium

    3 of 12 crawled pages have no meta description.

    3 affected URLs

    Write a description for each page, or generate one from its opening text.

  • The writing is readablemedium

    Median reading ease is 37.7 — difficult. 5 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.

       9.2 (very difficult)  https://novadose.com/product-category/metabolic/
      22.1 (very difficult)  https://novadose.com/product/klow-80mg-pen/
      24.8 (very difficult)  https://novadose.com/
      35.4 (difficult)  https://novadose.com/product-category/cartridges/
      37.7 (difficult)  https://novadose.com/privacy/

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

  • Page titles are unique

    All 12 crawled pages have distinct titles.

  • Every page is linked from somewhere

    All 12 crawled pages are reachable by internal links.

  • Pages have enough content

    All 12 crawled pages carry substantial content.

  • Images have alt text

    12 of 175 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.

  • No page type is thin across the board

    No template produces thin pages across all of its instances.

  • Missing pages return a real 404

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

  • Pages deliver what their titles promise

    Every page's body covers the subject its title and heading announce.

  • Meta descriptions are unique

    All 9 descriptions found are distinct.

  • Content identifies who wrote it

    Authorship is declared.

  • Links describe where they go

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

  • Every page is linked from another

    Every crawled page is linked from at least one other page.

  • 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.

  • Content carries recent dates

    6 of 12 crawled pages declare a date; the most recent is 2026-08-26.

  • One H1 per page

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

  • No long redirect chains

    No multi-step redirects found.

  • Sitemap matches the real site

    Sitemap lists 31 URLs; we reached 12 by crawling. 19 sitemap URLs were not linked from the pages we visited.

  • No dead-end pages

    Every crawled page links onward.

  • Internal authority is spread, not pooled

    Pages receive 7.9 internal links on average across the crawl, with no single page absorbing most of them.

  • A publisher is declared in structured data

    Publisher is declared in structured data.

  • 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.

17 passed · 3 failed · 3 skipped
82%
  • No lookalike domain can send mail as your brandhigh

    We generated and checked 60 plausible misspellings and variants of your domain. 1 of the 3 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.

    novadise.com   [mail configured]
    novadoes.com
    novados.com

    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.

  • Every submitted page is reachable by a linkmedium

    5 of 31 sitemap URL(s) were never reached by following links from the homepage. A sitemap makes a page known; links are what make it worth crawling and give it any authority at all. A page that exists only in the sitemap is one the site itself does not point at, which is the signal Google reads.

    /product-category/longevity/
    /product-category/metabolic/
    /product-category/recovery/
    /product-category/skin/
    /product-category/wellness/
    5 affected URLs

    Link them from a relevant hub, or remove them from the sitemap if they are not meant to rank.

  • 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.

  • Redundant nameservers

    2 nameserver(s) configured.

  • No subdomain can be taken over

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

  • Most of the site can be indexed

    26 of 29 crawled page(s) can be indexed (90%).

  • No unbounded URL spaces

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

  • No page type fails at a high rate

    Every template returns content for most of its URLs.

  • 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%).

  • The site is not buried

    The deepest page reached sits 2 click(s) from the homepage.

  • Certificate is not shared with unrelated domains

    Your certificate covers only your own domain.

  • Sitemap files are within Google's limits

    Every sitemap file is within the 50,000 URL and 50 MB limits.

  • Sitemap lastmod dates are meaningful

    31 of 32 sitemap URL(s) carry a lastmod date across 28 distinct value(s).

  • 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 AS13335 (CLOUDFLARENET - Cloudflare, Inc.), announced in 104.21.16.0/20 — a block of 4,096 addresses.

  • What this audit examined

    12 page(s) were examined, chosen to cover 11 of the 17 distinct page templates found across 32 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.

  • What this site is made of

    29 page(s) crawled across 15 template(s). Read the largest ones first — a fault in a template used four hundred times is a different size of problem from the same fault on one page, and the effort to fix it is the same.

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.

9 passed · 4 failed
72%
  • Largest Contentful Paint under 2.5s (lab)high

    Measured 3.5s on a simulated phone viewport. Google's threshold for 'good' is 2.5s. This is the metric most likely to be costing you both rankings and visitors who leave before the page paints.

    LCP 3496 ms · FCP 675 ms

    Compress and preload the largest above-the-fold image, and cache the HTML at the edge.

  • All page resources load successfullyhigh

    4 resource(s) failed to load. Missing images and stylesheets are visible to customers; missing scripts break features.

    https://connect.facebook.net/signals/config/941203915020301?v=2.9.390&r=stable&domain=novadose.com&hme=a767ae4c6a92a40ee4d7e358a937ad845c8bdb98a3bbe34 (failed)
    https://assets.novadose.com/videos/hero-lineup-prd.mp4 (failed)
    https://stats.g.doubleclick.net/g/collect?v=2&ngs=1&ibt=1&tid=G-73S83L6GG9&cid=1582777720.1788219629&gtm=45je68s1v9259966447za200zd9259966447&rcb=11&a (failed)
    https://www.google.com/ccm/collect?rcb=2&frm=0&apvc=1&auid=187419049.1788219629&dt=NovaDose%20%E2%80%94%20Pre-Filled%20Peptide%20Pens%2C%20Lab-Verifie (failed)
    4 affected URLs

    Fix or remove these URLs.

  • Tap targets are big enough to hitmedium

    53 of 74 tappable element(s) are smaller than 48x48 pixels, and 24 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.

    SAVE10 (70x21)
    NovaDose (113x32)
    Cart (40x40)
    Menu (40x40)
    A (350x44)

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

  • Body text is legible on a phonemedium

    125 of 268 text block(s) render below 12px on a mobile viewport. Text that small forces pinch-zooming, which is the single most common reason a visitor leaves a page on a phone before reading it.

    Set body text to at least 16px, and never below 12px.

  • Content is in the HTML, not built by JavaScript

    The served HTML contains 1664 words and the rendered page 1555 — 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.

  • JavaScript does not rewrite indexing directives

    The canonical and robots directives are the same before and after JavaScript runs.

  • Navigation links are crawlable without JavaScript

    93 links in the served HTML, 91 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.

  • 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.

  • Reasonable number of requests

    The page made 52 network requests to load.

Scan details

Final URLhttps://novadose.com/
Host IPs104.21.22.30, 172.67.202.49, 2606:4700:3030::6815:161e, 2606:4700:3030::ac43:ca31
Pages crawled12 of 12 attempted
Sitemap URLs32
Nameserversdaisy.ns.cloudflare.com, isaac.ns.cloudflare.com
Mail serversalt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx.l.google.com
DKIM selectorsgoogle, k2
Mail server IPs172.253.157.27, 142.250.102.26, 192.178.213.26
TLSTLSv1.3 · TLS_AES_256_GCM_SHA384 · issued by Google Trust Services
Detected stackWooCommerce / Cloudflare / Cloudflare · mail on Google Workspace · Google Analytics 4
Browser renderCamoufox (stealth Firefox) · 6.1s · 1555 words, 91 links after JavaScript
12 URLs crawled
  • https://novadose.com/
  • https://novadose.com/shop/
  • https://novadose.com/contact/
  • https://novadose.com/product/klow-80mg-pen/
  • https://novadose.com/lab-testing/
  • https://novadose.com/faq/
  • https://novadose.com/privacy/
  • https://novadose.com/product-category/cartridges/
  • https://novadose.com/product-category/metabolic/
  • https://novadose.com/product-category/longevity/
  • https://novadose.com/product-category/pens/
  • https://novadose.com/product-category/recovery/

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 novadose.com first.