getzapply.com website review

About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.9 s faster on a phone.

27 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

25 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (alia-prod.com, Google Tag Manager and Clarity and others), adding 2.4 MB and 1.3 s of main-thread time.

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

alia-prod.com costs a phone 432 ms of main-thread work and 725 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.

Google Tag Manager costs a phone 375 ms of main-thread work and 661 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.

The page has 1,510 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Klaviyo costs a phone 108 ms of main-thread work and 333 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.

Shopify costs a phone 68 ms of main-thread work and 311 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

22 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 34.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “EARLY BLACK FRIDAY Carl Froch Ex Boxing World Champion EARL…”.

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

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

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

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

34 images have no width and height attributes, so the layout jumps as each one loads.

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.

Your homepage downloads 9.7 MB in 482 requests on a phone: scripts 4.3 MB (137), images 3.5 MB (68) and other files 1.0 MB (198). Under 2 MB keeps phones on slow connections fast.

12 images are downloaded at several times the size a phone draws them, for example 2f1544818aa216da93dab7112522883fa100c123.png at 1,254 px wide, shown at 30 px. Resized copies would save about 830 KiB.

17 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

3 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

48 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

5 tap targets are too small or too close together to hit reliably with a finger.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

64 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (4 elements).

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

Your canonical URL points to tryzapply.com, not getzapply.com, so Google may credit that host instead.

Structured data found (Organization, ProductGroup and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("tiktok.com/@zapply.nl")”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 27 pages on getzapply.com and 15 external pages.

There is no https://getzapply.com/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.

Your homepage links to https://getzapply.com/tiktok.com/@zapply.nl, which answers with an error. Visitors hit a dead end and search engines drop it.

https://getzapply.com/products/zapply-tc-t1 and https://getzapply.com/products/testo-charge-90-capsules-gratis-e-book all use the title “Zapply T1 – Zapply UK”. Search engines can't tell which page to show for a search, so each competes with the others.

https://getzapply.com/products/zapply-tc-t1, https://getzapply.com/pages/frequently-asked-questions and https://getzapply.com/products/testo-charge-90-capsules-gratis-e-book have no meta description, so Google writes the search snippet from whatever text it finds.

https://getzapply.com/products/zapply-tc-t1, https://getzapply.com/pages/contact-1, https://getzapply.com/pages/frequently-asked-questions, https://getzapply.com/products/testo-charge-90-capsules-gratis-e-book and https://getzapply.com/pages/refund-policy have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

2 images failed to load on a phone, for example https://getzapply.com/.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

The homepage carries about 1,155 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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