robswagten.com website review

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

About 260 KiB 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.

1 image could be 9.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (website-files.com, Hotjar and Google Tag Manager and others), adding 10.4 MB and 1.4 s of main-thread time.

11 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

elfsightcdn.com costs a phone 205 ms of main-thread work and 9.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.

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

website-files.com costs a phone 477 ms of main-thread work and 316 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.

Hotjar costs a phone 329 ms of main-thread work and 65 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 3.3 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

7 KiB could be saved by minifying CSS.

8 long tasks block the main thread while loading, the longest for 153 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).

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

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

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

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

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

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

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 11.1 MB in 67 requests on a phone: images 9.6 MB (23), scripts 759 KiB (18) and fonts 454 KiB (9). Under 2 MB keeps phones on slow connections fast.

Rob.png weighs 9.5 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example Rob.png at 2,845 px wide, shown at 52 px. Resized copies would save about 9.4 MB.

1 image (9.5 MB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

65b7b57c31bf37f55d020a44_Round circle background.svg 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).

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

All page content should be contained by landmarks: 70 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.

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

Your title is 77 characters, so Google will cut it off around 60: “Datagedreven website ontwikkeling voor SaaS Scaleup | Rob Swagten | Amsterdam”.

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

There are 2 <h1> headlines (“Data-driven Web Design To Unlock New Growth For T…” and “Rob Swagten”). One clear main headline is easier for people and search engines.

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

Your meta description is 234 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 42 pages on robswagten.com 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://www.robswagten.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://www.robswagten.com/oud/homepagina-old, https://www.robswagten.com/projecten/fotomeid, https://www.robswagten.com/projecten/rebalance-massage, https://www.robswagten.com/oud/over-mij and https://www.robswagten.com/oud/old-home-2, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.robswagten.com/eng/home is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.robswagten.com/projecten/emlen, https://www.robswagten.com/projecten/binqy and https://www.robswagten.com/projecten/yutu-grow all use the title “Rob Swagten | Web Design Services”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.robswagten.com/projecten/emlen, https://www.robswagten.com/projecten/binqy, https://www.robswagten.com/projecten/yutu-grow and https://www.robswagten.com/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image is served at too low a resolution for sharp phone screens.

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

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 1,782 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Hotjar (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 14 cookies, 1 of them by other companies (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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.