wearenew.nl website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and cdn-cookieyes.com and others), adding 942 KiB and 623 ms of main-thread time.

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

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

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

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

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

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

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

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

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 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We gebruiken cookies om uw browse-ervaring te verbeteren, g…”. Most of its time is element render delay (5.5 s).

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

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

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

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

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

The layout shifts by 0.111 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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 2.1 MB in 111 requests on a phone: scripts 1.1 MB (40), images 788 KiB (31) and HTML 121 KiB (1). Under 2 MB keeps phones on slow connections fast.

4 images further down the page (708 KiB) 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 0.61 g of CO₂e: 72.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

4 visible links have no text or label, so screen readers cannot say where they go.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

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

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

The homepage links to 103 pages on wearenew.nl and 10 external pages.

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.

There is no https://wearenew.nl/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.

https://wearenew.nl/over-ons/creative-playground is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://wearenew.nl/diensten, https://wearenew.nl/diensten/branding, https://wearenew.nl/diensten/campagnes-activaties, https://wearenew.nl/diensten/contentcreatie, https://wearenew.nl/diensten/food-marketing and https://wearenew.nl/ons-werk and 3 others 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.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

The homepage carries about 411 words of visible text.

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

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

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