thomaslammens-gd.com website review

5 images could be 411 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

About 159 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 760 ms faster on a phone.

cloudfront.net costs a phone 0 ms of main-thread work and 466 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.

5 third-party services load with your homepage (Google Tag Manager, jQuery CDN and fontlibrary.org and others), adding 787 KiB and 141 ms of main-thread time.

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

3 KiB could be saved by minifying CSS.

1 long task block the main thread while loading, the longest for 82 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.

Your largest element takes 7.2 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 7.3 s. Good is under 3.8 s.

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

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

competences.gif weighs 28.3 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example competences.gif at 1,982 px wide, shown at 332 px. Resized copies would save about 21.3 MB.

Your homepage downloads 5.2 MB in 40 requests on a phone: images 4.8 MB (28), scripts 351 KiB (6) and fonts 14 KiB (2). Under 2 MB keeps phones on slow connections fast.

2 images (28.7 MB) are 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.

1 image further down the page (28.3 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 14 characters: “Thomas Lammens”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.thomaslammens-gd.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at thomaslammens-gd.com/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 13 pages on thomaslammens-gd.com and 4 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.thomaslammens-gd.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.

https://www.thomaslammens-gd.com/plantasia, https://www.thomaslammens-gd.com/clnk, https://www.thomaslammens-gd.com/bas, https://www.thomaslammens-gd.com/sorrychildren, https://www.thomaslammens-gd.com/emakina and https://www.thomaslammens-gd.com/inwild and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.thomaslammens-gd.com/plantasia, https://www.thomaslammens-gd.com/clnk, https://www.thomaslammens-gd.com/bas, https://www.thomaslammens-gd.com/sorrychildren, https://www.thomaslammens-gd.com/emakina and https://www.thomaslammens-gd.com/inwild and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.thomaslammens-gd.com/plantasia, https://www.thomaslammens-gd.com/clnk, https://www.thomaslammens-gd.com/bas, https://www.thomaslammens-gd.com/sorrychildren, https://www.thomaslammens-gd.com/emakina and https://www.thomaslammens-gd.com/inwild and 5 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

2 errors were logged to the browser console while the page loaded, for example “s is not defined”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 304 words of visible text.

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