a2zsync.com website review

• Reduce unused JavaScript

  1.3 s · 454 KiB

  About 454 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.

• Mobile performance score: 56

  56/100

  Your mobile performance score is 56 (desktop: 85). Pages that score under 90 lose visitors before the first paint.

• 3 third-party services on the page

  3 third-party services load with your homepage (Google Tag Manager, OptiMonk and Google Analytics), adding 403 KiB and 942 ms of main-thread time.

• Use efficient cache lifetimes

  650 ms · 236 KiB

  5 files are served with short cache lifetimes, so returning visitors download them again (236 KiB).

• Google Tag Manager adds 577 ms

  577 ms

  Google Tag Manager costs a phone 577 ms of main-thread work and 290 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

• OptiMonk adds 365 ms

  365 ms

  OptiMonk costs a phone 365 ms of main-thread work and 112 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

• 13 long tasks on the main thread

  13 long tasks block the main thread while loading, the longest for 269 ms. During a long task the page ignores taps.

• Main-thread work: 2.4 s

  A phone's processor spends 2.4 s on main-thread work while loading, 928 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

• Legacy JavaScript

  150 ms · 21 KiB

  Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

• Reduce unused CSS

  160 ms · 11 KiB

  About 11 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.

• Duplicated JavaScript

  150 ms · 17 KiB

  17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

• Render-blocking requests

  150 ms

  1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

• Phones get a much slower page than desktops

  Desktop scores 85 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.

• Chained critical requests

  Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

• Forced reflow

  Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

• Speed Index: 7.1 s

  7.1 s

  Visually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.

• Largest Contentful Paint: 4.7 s

  4.7 s

  Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SOMETHING REVOLUTIONARY IS TAKING SHAPE. A2Z SYNC DEALER EX…”. Most of its time is element render delay (4.4 s).

  Show on pageElements (1)

• Total Blocking Time: 654 ms

  654 ms

  Scripts block taps and scrolling for 654 ms in total while the page loads. Good is under 200 ms.

• First Contentful Paint: 2.7 s

  2.7 s

  The first text or image appears after 2.7 s on a phone. Good is under 1.8 s.

• Time to Interactive: 5.7 s

  5.7 s

  The page becomes fully interactive after 5.7 s. Good is under 3.8 s.

• Not enough real-visitor data yet

  Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

• Page weight: 5.6 MB in 17 requests

  5.6 MB

  Your homepage downloads 5.6 MB in 17 requests on a phone: media 4.5 MB (1), scripts 609 KiB (6) and images 236 KiB (5). Under 2 MB keeps phones on slow connections fast.

• About 1.6 g of CO₂ per visit

  1.57 g

  By the Sustainable Web Design model, a visit to your homepage emits about 1.57 g of CO₂e: 189.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Not measured in this review.

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• No structured data

  No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

• No canonical URL

  No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

• Only 0 internal links

  The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

• No Organization structured data

  There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

• No llms.txt

  There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

• 3 small tap targets

  3 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• Missing source maps

  Large scripts ship without source maps.

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• No clickjacking protection

  Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  a2zsync.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  a2zsync.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• No calls to action

  We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

• Only about 57 words

  The homepage has only about 57 words of visible text; thin pages give Google and first-time buyers little to go on.

• No form on the homepage

  There is no form on the homepage, so every lead has to click through to another page first.

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be a2zsync.com is still delivered. Reports are on, so moving to quarantine is the next step.

• Email authentication score: 70/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 2 trackers load before any consent

  2

  Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

• 8 cookies set on arrival

  8

  Opening the homepage sets 8 cookies, 1 of them by other companies (measured from a US location before any click).

• No consent tool detected

  No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

• 9 other companies contacted

  Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.