tryzapply.com website review

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

24 images could be 1.6 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.2 s.

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

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

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

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

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

alia-prod.com costs a phone 422 ms of main-thread work and 726 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 335 ms of main-thread work and 658 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.

heatmap.com costs a phone 281 ms of main-thread work and 162 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.

Klaviyo costs a phone 150 ms of main-thread work and 332 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 77 ms of main-thread work and 488 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.

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

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

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

Polyfills for old browsers add 74 KiB JavaScript that modern phones do not need.

21 KiB could be saved by minifying JavaScript.

About 15 KiB of CSS is downloaded but never applied on this page.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 15.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…”.

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

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

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

Scripts block taps and scrolling for 504 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.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 138 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.5 MB in 585 requests on a phone: scripts 4.5 MB (137), images 3.5 MB (72) and other files 1.6 MB (297). 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 831 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.98 g of CO₂e: 358.2 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.

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

7 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: 6 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.

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 30 pages on tryzapply.com and 12 external pages.

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.

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

/products/zapply-tc-t1, /a/loop_subscriptions/customer and /pages/frequently-asked-questions have no meta description, so Google writes the search snippet from whatever text it finds.

/products/zapply-tc-t1, /a/loop_subscriptions/customer, /pages/contact-1 and /pages/frequently-asked-questions have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 11 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://tryzapply.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.

1 link from your homepage to your own site is broken, for example https://tryzapply.com/tiktok.com/@zapply.nl (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://instagram.com/zapply_?igshid=YmMyMTA2M2Y=.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

tryzapply.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 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,343 words of visible text.

DMARC is set to p=none, so mail pretending to be tryzapply.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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.

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 37 cookies (measured from a US location before any click).

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