Skip to report
SpyOnAds by Fire Pixel
Scan another domain

Competitor intelligence dossier

Doxzoo: Document Printing & Binding

doxzoo.com

Bring documents to life with Doxzoo - your online printing service. Instant quotes, free UK delivery over £30 & 10% discount on your first 2 orders!

ObservedScanned 4 September 2026 at 10:06 UTCOpen sampled website ↗

60-second brief

The useful bits first

What the site appears to sell, how it converts visitors, what is measurable and where the evidence is incomplete.

Verified public adsNeeds verification
No verified match

No matching public ad was verified in the sampled libraries. This does not prove that no campaigns are running.

Show evidence
  • Bounded public ad-library checks; unmatched records were excluded
Measurement stackObserved
Meta Pixel, Microsoft UET and TikTok Pixel

5 public measurement or advertising signals were observed. Presence does not prove configuration quality or report receipt.

Show evidence
  • Meta Pixel observed
  • Microsoft UET observed
  • TikTok Pixel observed
  • Google tag / GA4 observed
Platform and edgeObserved
Cloudflare

Cloudflare was observed at the public edge. The origin host may remain hidden.

Show evidence
  • Cloudflare: CDN and WAF
Backlink authorityObserved
DR 42

Ahrefs Domain Rating is a logarithmic backlink-strength metric. It is not a traffic estimate or a search-position score.

Show evidence
PerformanceObserved
65 mobile lab

Mobile lab scored 65 out of 100. Lighthouse reported a 3 ms server response in that run.

Show evidence
  • Mobile lab: 65/100
  • Lighthouse server response: 3 ms
  • Bounded scanner page fetch: 118 ms

Commercial read

What they appear to be doing

A cautious interpretation of the public positioning, offers, proof, conversion routes, acquisition signals and content footprint.

ProofNeeds verification

No case-study, testimonial or review proof was confirmed in the bounded sample.

Conversion routesObserved

Website form and Marketing or CRM route were observed. Submission handling and conversion firing were not tested.

Show evidence
  • Public forms with 14 distinct field names
AcquisitionInferred

Meta, Microsoft Advertising, TikTok and Google measurement or advertising technology is present. This suggests channel instrumentation, but does not prove that campaigns are active.

Show evidence
  • Meta Pixel observed
  • Microsoft UET observed
  • TikTok Pixel observed
  • Google tag / GA4 observed
Content footprintObserved

618 words were found on the sampled homepage. 5 exact-domain pages appeared in the bounded index-presence check.

Show evidence

Prioritised

Next moves worth making

Up to five practical actions, deduplicated and ordered by likely impact. Open each one for the evidence and verification path.

  1. 39 images have no alt attribute

    high impactObserved

    Add contextual alternatives to informative images and empty alt text to decorative ones.

    Show evidence and next steps

    Why it matters: Images without an alt attribute can be announced poorly or lose equivalent content for screen-reader users.

    What we found:
    • Static HTML image inventory

    How to verify: Review the rendered accessibility tree and screen-reader output.

    Confidence: highSuggested owner: DeveloperEstimated effort: hours

  2. 1 sampled fields lack an explicit accessible label

    high impactInferred

    Associate visible labels with controls or supply an equivalent accessible name.

    Show evidence and next steps

    Why it matters: Labels make controls understandable and enlarge the reliable interaction target.

    What we found:
    • Static label, aria-label and aria-labelledby checks

    How to verify: Inspect each rendered control in the accessibility tree.

    Confidence: mediumSuggested owner: DeveloperEstimated effort: hours

  3. 11 potentially parser-blocking external scripts

    medium impactInferred

    Use defer, async or modules where dependency ordering allows.

    Show evidence and next steps

    Why it matters: Parser-blocking scripts can delay initial rendering. Browser preload and response timing can change the actual effect.

    What we found:
    • accounts.google.com
    • ajax.googleapis.com
    • api.goaffpro.com
    • apis.google.com
    • doxzoo.com
    • static.klaviyo.com
    • use.typekit.net
    • widget.reviews.io

    How to verify: Confirm with a Lighthouse trace and rendered waterfall.

    Confidence: mediumSuggested owner: DeveloperEstimated effort: hours

Speed and experience

Performance with honest limits

Lighthouse is a one-off lab test. CrUX is 28-day real-user data and may be unavailable on lower-traffic sites.

Current read65 mobile lab

Mobile lab scored 65 out of 100. Lighthouse reported a 3 ms server response in that run.

Mobile lab 65 / 100

Controlled Lighthouse lab result.

  • LCP2.8 s
  • CLS0.048
  • TBT850 ms
  • FCP2.6 s
Desktop lab 59 / 100

Controlled Lighthouse lab result.

  • LCP1.6 s
  • CLS0.022
  • TBT1,150 ms
  • FCP0.8 s
Real-user Core Web Vitals

Public real-user field data was returned.

Observed
Open full Lighthouse and Core Web Vitals evidence

Performance and Core Web Vitals

Core Web Vitals are LCP, INP and CLS measured from real users at the 75th percentile. Lighthouse is a synthetic test: it can diagnose LCP and CLS, while TBT is only a laboratory proxy for responsiveness and is not INP.

Current read

The available real-user profiles pass Core Web Vitals. Lighthouse remains a diagnostic snapshot, not the field verdict.

Lighthouse lab diagnostics

Synthetic lab test

Mobile Lighthouse

Needs improvement
65/ 100

A one-off Lighthouse diagnostic. A score of 90 or higher is considered good, but it is not a real-user Core Web Vitals verdict.

LCP2.8 sNeeds improvement
CLS0.048Good
TBT850 msPoor · lab proxy, not INP
FCP2.6 sNeeds improvement
Speed Index7.0 sPoor
Show mobile Lighthouse diagnostics and fixes
  • Reduce unused CSS

    Remove unused styles, split page-specific CSS and load non-critical styles after the first render. Estimated lab saving: up to 150 ms · 92.7 KB.

  • Minify JavaScript

    Open the Lighthouse diagnostic, address the largest estimated saving first, then rerun the same page and device profile. Estimated lab saving: 155 KB.

  • Reduce unused JavaScript

    Remove dead JavaScript, split large bundles and defer code that is not needed for the first view. Estimated lab saving: 1 MB.

Source: Google PageSpeed Insights / Lighthouse · Profile: mobile · Tested: 4 September 2026 at 10:05 UTC · Lighthouse 13.4.1 · tested page

Synthetic lab test

Desktop Lighthouse

Needs improvement
59/ 100

A one-off Lighthouse diagnostic. A score of 90 or higher is considered good, but it is not a real-user Core Web Vitals verdict.

LCP1.6 sNeeds improvement
CLS0.022Good
TBT1,150 msPoor · lab proxy, not INP
FCP0.8 sGood
Speed Index2.4 sPoor
Show desktop Lighthouse diagnostics and fixes
  • Reduce unused CSS

    Remove unused styles, split page-specific CSS and load non-critical styles after the first render. Estimated lab saving: up to 210 ms · 92.4 KB.

  • Reduce unused JavaScript

    Remove dead JavaScript, split large bundles and defer code that is not needed for the first view. Estimated lab saving: up to 100 ms · 1 MB.

  • Minify JavaScript

    Open the Lighthouse diagnostic, address the largest estimated saving first, then rerun the same page and device profile. Estimated lab saving: 155 KB.

Source: Google PageSpeed Insights / Lighthouse · Profile: desktop · Tested: 4 September 2026 at 10:05 UTC · Lighthouse 13.4.1 · tested page

Real-user Core Web Vitals

Real users · rolling 28 days

Mobile real-user Core Web Vitals

Passes
Passes Core Web Vitals

75th-percentile Chrome experience · exact URL · 6 Aug 2026 to 2 Sept 2026.

LCP1.1 sGood · Good at 2.5 s or faster
INP186 msGood · Good at 200 ms or faster
CLS0.02Good · Good at 0.1 or lower
Show mobile CrUX evidence and fixes

No Core Web Vitals fix is indicated by this public sample. Keep monitoring because the rolling 28-day result changes over time.

Source: Chrome UX Report API · CrUX eligibility methodology

Real users · rolling 28 days

Desktop real-user Core Web Vitals

Passes
Passes Core Web Vitals

75th-percentile Chrome experience · exact URL · 6 Aug 2026 to 2 Sept 2026.

LCP924 msGood · Good at 2.5 s or faster
INP104 msGood · Good at 200 ms or faster
CLS0.02Good · Good at 0.1 or lower
Show desktop CrUX evidence and fixes

No Core Web Vitals fix is indicated by this public sample. Keep monitoring because the rolling 28-day result changes over time.

Source: Chrome UX Report API · CrUX eligibility methodology

What to fix or verify

  • Desktop: Reduce unused CSS

    Remove unused styles, split page-specific CSS and load non-critical styles after the first render. Estimated lab saving: up to 210 ms · 92.4 KB.

  • Mobile: Reduce unused CSS

    Remove unused styles, split page-specific CSS and load non-critical styles after the first render. Estimated lab saving: up to 150 ms · 92.7 KB.

  • Desktop: Reduce unused JavaScript

    Remove dead JavaScript, split large bundles and defer code that is not needed for the first view. Estimated lab saving: up to 100 ms · 1 MB.

SEO baseline75Google Lighthouse mobile
Accessibility baseline73Google Lighthouse mobile · manual follow-up still required

Receipts

Technical evidence

The supporting stack, measurement, infrastructure, reputation and raw collection modules. Kept compact until you need it.

Technology fingerprints11

Meta Pixel · Universal Event Tracking · TikTok Pixel · Google tag, GA4, Ads or Floodlight · Cloudflare

Measurement signals5

Meta Pixel · Microsoft UET · TikTok Pixel · Google tag / GA4 · Google Tag Manager

Hosting / edgeCloudflare

Cloudflare was observed at the edge. The origin hosting provider may be hidden behind it.

Open stack, registration and safety evidence

Technology and measurement fingerprints

Meta Pixel · AdvertisingUniversal Event Tracking · AdvertisingTikTok Pixel · AdvertisingGoogle tag, GA4, Ads or Floodlight · Analytics and dataCloudflare · CDN and edgeCookieYes CMP · Consent managementCloudflare DNS · DNS providerKlaviyo onsite tracking · Marketing and CRMContainer bootstrap · Tag managementBootstrap · UI frameworkGoogle Fonts · Web fonts

Hosting, registration and authority

Hosting or edge
Cloudflare
Registered domain
doxzoo.com
Registrar
IONOS SE (83)
Registered
31 May 2013 at 12:00 UTC
Expires
31 May 2027 at 12:00 UTC
Domain Rating · Domain Rating by Ahrefs
42 / 100

Reputation check

Google Web Risk
No current Google Web Risk match

No match is not a safety guarantee. Investigate any warning independently.

Open all evidence modules and methodology

Evidence and key metrics

Open any card to inspect the public evidence, source and collection details.

Public page and headers

2pages fetched

185.2 KB of public HTML inspected

Show evidence

HTTP 200 · 131.5 KB · 118 ms · view sampled page

HTTP 200 · 53.7 KB · 94 ms · view sampled page

Source: Direct fetch · Collected in 118 ms

Rendered browser and network

2pages rendered

351 browser requests observed before interaction

Show evidence

HTTP 200 · 196 requests · 20 third-party hosts · view sampled page

HTTP 200 · 155 requests · 25 third-party hosts · view sampled page

Fresh browser context; no forms or logins submitted

Source: Hardened Chromium provider · Collected in 8.6 s

Technology fingerprinting

11technologies

Meta Pixel · Universal Event Tracking · TikTok Pixel

Show evidence

Meta Pixel · Advertising · 100% confidence

Universal Event Tracking · Advertising · 100% confidence

TikTok Pixel · Advertising · 100% confidence

Google tag, GA4, Ads or Floodlight · Analytics and data · 100% confidence

Cloudflare · CDN and edge · 100% confidence

CookieYes CMP · Consent management · 100% confidence

Cloudflare DNS · DNS provider · 100% confidence

Klaviyo onsite tracking · Marketing and CRM · 100% confidence

Source: First-party signatures and public container evidence

DNS and email records

18DNS records

4 addresses · 2 nameservers · 2 mail routes

Show evidence

Domain: doxzoo.com

A: 2 records

AAAA: 2 records

NS: 2 records

MX: 2 records

TXT: 9 records

SOA: 1 record

Email policy: SPF present · DMARC not observed

Source: DNS over HTTPS · Coverage: Partial coverage · Collected in 312 ms

WHOIS / registration

doxzoo.com13.3 years old

Registration currently expires 31 May 2027

Show evidence

Registrar: IONOS SE (83)

Registered: 31 May 2013

Expires: 31 May 2027

Nameservers: dan.ns.cloudflare.com, sima.ns.cloudflare.com

Registry RDAP via the IANA bootstrap · https://rdap.verisign.com/com/v1/domain/doxzoo.com

Source: Registry RDAP via the IANA bootstrap

IP allocation and hosting

CloudflareCDN and WAF

172.66.40.59

Show evidence

Network allocation: CLOUDFLARENET

Address: 172.66.40.59

Edge detection confidence: high

Cloudflare was observed at the edge. The origin hosting provider may be hidden behind it.

Source: IP RDAP · Collected in 880 ms

Lighthouse and Core Web Vitals

65/ 100

Mobile Lighthouse performance

Show evidence

FCP: 2.6 s

LCP: 2.8 s

CLS: 0.048

TBT: 850 ms

Mobile real-user Core Web Vitals: Passes · url scope

Desktop real-user Core Web Vitals: Passes · url scope

Top lab opportunity: Reduce unused CSS · up to 150 ms · 92.7 KB

Source: Google PSI and CrUX · Collected in 35 s

Google Web Risk

0threat matches

No current Google Web Risk match

Show evidence

Google Web Risk: no current match

Reputation data is a provider snapshot, not a warranty that a site is safe. Timestamps and coverage matter.

Source: Google Web Risk · Coverage: Partial coverage · Collected in 68 ms

Backlink authority

42/ 100

Backlink profile strength on a logarithmic 0-100 scale. It is not a Google ranking or traffic metric.

Show evidence

Target domain: doxzoo.com

Domain Rating by Ahrefs · https://ahrefs.com/

Scale: 0–100 · logarithmic

Source: Domain Rating by Ahrefs · Collected in 109 ms

robots.txt

0disallow rules

robots.txt found · 0 sitemap declarations

Show evidence

robots.txt · 99 B · view sampled page

User-agent directives: not observed

Source: Direct public fetch

XML sitemap sample

Check failed

No default XML sitemap was returned

Show evidence

Default sitemap · 0 B · view sampled page

Entries in bounded sample: 0

Source: Direct public fetch · Coverage: Check failed

security.txt

Not found

No file returned from the standard public location

Show evidence

Checked /.well-known/security.txt · view sampled page

Absence is informational and is not a vulnerability by itself

Source: Direct public fetch · Coverage: Not found

Scoring and action plan

81/ 100

14 priority findings · 96% scored evidence coverage

Show evidence

Deterministic ruleset 0.1.0

Report generated: 4 September 2026 at 10:06 UTC

Rules produced 14 prioritised findings

Source: Deterministic ruleset 0.1.0

All corrected findings

  • 1 sampled fields lack an explicit accessible labelhigh

    5 forms were inspected with static label heuristics.

    Suggested fix: Associate visible labels with controls or supply an equivalent accessible name.

    Show evidence and next steps

    Why it matters: Labels make controls understandable and enlarge the reliable interaction target.

    What we found:
    • Static label, aria-label and aria-labelledby checks

    How to verify: Inspect each rendered control in the accessibility tree.

    Confidence: inferredSuggested owner: DeveloperEstimated effort: hours

  • 11 potentially parser-blocking external scriptshigh

    16 external script tags were found in source HTML.

    Suggested fix: Use defer, async or modules where dependency ordering allows.

    Show evidence and next steps

    Why it matters: Parser-blocking scripts can delay initial rendering. Browser preload and response timing can change the actual effect.

    What we found:
    • accounts.google.com
    • ajax.googleapis.com
    • api.goaffpro.com
    • apis.google.com
    • doxzoo.com
    • static.klaviyo.com

    How to verify: Confirm with a Lighthouse trace and rendered waterfall.

    Confidence: inferredSuggested owner: DeveloperEstimated effort: hours

  • 39 images have no alt attributehigh

    42 image elements were inspected. Empty alt text is counted separately from a missing attribute.

    Suggested fix: Add contextual alternatives to informative images and empty alt text to decorative ones.

    Show evidence and next steps

    Why it matters: Images without an alt attribute can be announced poorly or lose equivalent content for screen-reader users.

    What we found:
    • Static HTML image inventory

    How to verify: Review the rendered accessibility tree and screen-reader output.

    Confidence: observedSuggested owner: DeveloperEstimated effort: hours

  • Lighthouse accessibility baseline: 73medium

    The current automated score is 73 out of 100.

    Suggested fix: Review the failed automated audits, then complete manual keyboard and assistive-technology testing.

    Show evidence and next steps

    Why it matters: A lab score is a controlled diagnostic snapshot, not a real-user outcome.

    What we found:
    • Google Lighthouse mobile accessibility category

    How to verify: Rerun with the same strategy after changes and compare the underlying audits.

    Confidence: observedSuggested owner: DeveloperEstimated effort: days

  • Mobile Lighthouse performance: 65medium

    The current automated score is 65 out of 100.

    Suggested fix: Improve the largest Lighthouse opportunities, then rerun the same mobile test.

    Show evidence and next steps

    Why it matters: A lab score is a controlled diagnostic snapshot, not a real-user outcome.

    What we found:
    • Google Lighthouse mobile lab test

    How to verify: Rerun with the same strategy after changes and compare the underlying audits.

    Confidence: observedSuggested owner: DeveloperEstimated effort: days

  • Desktop Lighthouse performance: 59medium

    The current automated score is 59 out of 100.

    Suggested fix: Address the largest repeatable lab bottlenecks and retest.

    Show evidence and next steps

    Why it matters: A lab score is a controlled diagnostic snapshot, not a real-user outcome.

    What we found:
    • Google Lighthouse desktop lab test

    How to verify: Rerun with the same strategy after changes and compare the underlying audits.

    Confidence: observedSuggested owner: DeveloperEstimated effort: days

  • Lighthouse SEO baseline: 75medium

    The current automated score is 75 out of 100.

    Suggested fix: Review failed Lighthouse SEO audits and verify indexability manually.

    Show evidence and next steps

    Why it matters: A lab score is a controlled diagnostic snapshot, not a real-user outcome.

    What we found:
    • Google Lighthouse mobile SEO category

    How to verify: Rerun with the same strategy after changes and compare the underlying audits.

    Confidence: observedSuggested owner: SEOEstimated effort: hours

  • No click-ID field was visible on sampled formsmedium

    7 forms were observed; 0 exposed a supported click-ID field.

    Suggested fix: Verify click IDs are captured, stored on the CRM record and returned with eligible outcomes.

    Show evidence and next steps

    Why it matters: Persisting ad click identifiers can make later qualified outcomes joinable to the original ad interaction.

    What we found:
    • Public form field names only

    How to verify: Submit an authorised test lead manually and inspect the receiving record.

    Confidence: inferredSuggested owner: MarketerEstimated effort: hours

  • 39 images lack an alt attributemedium

    42 image elements were inspected in source HTML.

    Suggested fix: Add meaningful alt text to informative images and empty alt to decorative images.

    Show evidence and next steps

    Why it matters: Alternative text supports accessibility and image understanding.

    What we found:
    • /assets/arrow-up-white-84fd0126e46858d31789a02393ebf2d3ce9d7309deb10fd606b7c6e92a94f252.svg
    • /assets/clients/doxzoo/icons/icon-upload-7d9662aca0d81552519ef5c6eca5ca4586baed858b93fb7c754e6adddd64cfe6.svg
    • /assets/clients/doxzoo/icons/icon-instant-quote-42bcc0e66ee0e77884080318cc5376a9a471b18d5290b9efe6ebd35cbaebd6e4.svg
    • https://doxzoo-library.imgix.net/library_images/files/000/003/819/carousel/Home_Carousel.png?ixlib=rb-4.1.0&auto=format&fm=webp&max_w=801.0&max_h=441.0&fit=fill
    • https://doxzoo-library.imgix.net/library_images/files/000/001/709/carousel/carousel_%2823%29.png?ixlib=rb-4.1.0&auto=format&fm=webp&max_w=801.0&max_h=441.0&fit=

    How to verify: Review each image in context with accessibility tooling.

    Confidence: observedSuggested owner: SEOEstimated effort: hours

  • Heading levels are skipped in source ordermedium

    H1 to H3, H2 to H4, H2 to H4, H2 to H5

    Suggested fix: Use headings to represent nested document structure, not visual size.

    Show evidence and next steps

    Why it matters: A logical heading outline helps keyboard and screen-reader navigation.

    What we found:
    • Static heading order

    How to verify: Inspect the rendered heading outline.

    Confidence: inferredSuggested owner: DeveloperEstimated effort: hours

  • No canonical link observedmedium

    The sampled HTML did not include a canonical link.

    Suggested fix: Declare the preferred public URL and keep it aligned with sitemap and internal links.

    Show evidence and next steps

    Why it matters: Canonical declarations help consolidate duplicate URL signals.

    What we found:
    • Canonical link absent

    How to verify: Compare the final URL, canonical and sitemap entry.

    Confidence: observedSuggested owner: SEOEstimated effort: minutes

  • No default or robots-declared sitemap was confirmedmedium

    No default or robots-declared sitemap was confirmed

    Suggested fix: Publish and reference an XML sitemap with canonical URLs.

    Show evidence and next steps

    Why it matters: Sitemaps help discovery and communicate canonical URLs.

    What we found:
    • robots.txt and /sitemap.xml sample

    How to verify: Repeat the same public check after the change.

    Confidence: observedSuggested owner: SEOEstimated effort: minutes

  • Permissions policy not observedmedium

    The header was absent from the sampled final HTML response.

    Suggested fix: Set a restrictive Permissions-Policy for unused browser capabilities.

    Show evidence and next steps

    Why it matters: Permissions-Policy limits access to powerful browser features.

    What we found:
    • Final HTTP response headers

    How to verify: Inspect the final response headers after deployment.

    Confidence: observedSuggested owner: DeveloperEstimated effort: hours

  • No DNSSEC DS record observedlow

    No DS record was returned. This does not test every resolver or validate the complete chain.

    Suggested fix: Consider enabling DNSSEC with coordinated registrar and DNS-provider configuration.

    Show evidence and next steps

    Why it matters: DNSSEC can provide origin authentication for DNS answers when the validation chain is correct.

    What we found:
    • DS query through DNS over HTTPS

    How to verify: Validate the complete chain with an independent DNSSEC tool.

    Confidence: inferredSuggested owner: ITEstimated effort: hours

Methodology and limitations

Bounded analysis of publicly accessible pages, DNS, registries and configured providers. No login, form submission, port scan or exploit testing.

  • The report is a bounded public sample, not a complete crawl, account audit, accessibility certification, legal compliance review or penetration test.
  • Technology and hosting detections are confidence-ranked fingerprints. They do not prove ownership, configuration quality, exact version or vulnerability.
  • A browser request shows that the page attempted a destination. It does not prove storage, reporting, attribution or use by an advertising algorithm.
  • The public scanner does not log in, submit forms, complete checkout, download files, scan ports or test exploits.