gartec.com website review

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

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

About 825 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.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 6.1 MB and 502 ms of main-thread time.

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

Vimeo costs a phone 85 ms of main-thread work and 5.4 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.

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

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

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

Google Tag Manager costs a phone 156 ms of main-thread work and 352 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 long tasks block the main thread while loading, the longest for 115 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).

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

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.

3 KiB could be saved by minifying CSS.

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.

Real visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your browsing experience, serve p…”.

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

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

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

Real visitors wait 237 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

8 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-17, real Chrome visitors' tap response (inp) went from 224 ms to 243 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 8.3 MB in 156 requests on a phone: other files 5.3 MB (19), scripts 1.7 MB (56) and images 935 KiB (26). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example home-lift-range.png at 1,314 px wide, shown at 390 px. Resized copies would save about 384 KiB.

3 images further down the page (549 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (464 KiB) 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.

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

1 button has no accessible name, so screen readers announce just “button”.

1 element hidden from screen readers can still receive keyboard focus.

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

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Structured data found (Organization) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 105 pages on gartec.com and 7 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.

/case-studies has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /contact, whose canonical is /contact-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/goods-lift-range and /lift-emergency-phone-upgrade-analogue-switch-off have no <h1> headline, so visitors and search engines get no clear main topic.

/goods-lift-range, /step-lift-range, /lift-servicing, /servicing-packages, /lift-refurbishment and /lift-replacement and 1 other took over 3 s to send their HTML from our server.

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

4 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'blur')”.

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

Chrome logged issues while loading the page (“Cookie”).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

1 link go through two or more redirects, for example https://facebook.com/gartecltd.

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.

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

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

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

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

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.

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.

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

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 Tag Manager, Meta Pixel, Microsoft Ads and Microsoft Clarity (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 12 cookies, 2 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.