evertee.nl website review

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

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

8 third-party services load with your homepage (Shopify, Clarity and loox.io and others), adding 3.0 MB and 1.1 s of main-thread time.

Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

3 images could be 128 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

15 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

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

Shopify costs a phone 309 ms of main-thread work and 1.6 MB 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,728 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google Tag Manager costs a phone 137 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.

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

rebuyengine.com costs a phone 97 ms of main-thread work and 298 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.

azurefd.net costs a phone 58 ms of main-thread work and 331 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 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

21 KiB could be saved by minifying JavaScript.

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

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 25.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A t-shirt for life. Guaranteed. We guarantee each t-shirt f…”.

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

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

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

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 5.3 MB in 531 requests on a phone: scripts 2.6 MB (190), other files 1.9 MB (286) and images 313 KiB (9). Under 2 MB keeps phones on slow connections fast.

trust-pilot.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example landing-banner.png at 1,536 px wide, shown at 390 px. Resized copies would save about 57 KiB.

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

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

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

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

Your <h1> is empty.

The homepage links to 47 pages on evertee.nl and 9 external pages.

https://www.evertee.us/products/black-t-shirt-friday and https://www.evertee.us/products/mystery-3-premium-evertee-bundle are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.evertee.us/pages/stock-evertee, https://www.evertee.us/pages/activate-your-guarantee, https://www.evertee.us/policies/privacy-policy and https://www.evertee.us/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.evertee.us/products/evertee-original%C2%AE and https://www.evertee.us/products/evertrade%C2%AE-tee use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.evertee.us/products/evertee-original%C2%AE, whose canonical is https://www.evertee.us/products/evertee-original%c2%ae. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.evertee.us/products/evertee-original%C2%AE, https://www.evertee.us/pages/stock-evertee and https://www.evertee.us/pages/activate-your-guarantee have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 412 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.

Opening the homepage sets 20 cookies (measured from a US location before any click).

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.

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