ingemat.com website review

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

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

About 250 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

5 images could be 320 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

2 third-party services load with your homepage (FontAwesome CDN and Google Fonts), adding 196 KiB and 0 ms of main-thread time.

15 KiB could be saved by minifying CSS.

Desktop scores 83 but mobile only 58. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ingemat”.

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

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

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

Your homepage downloads 3.1 MB in 107 requests on a phone: images 1.4 MB (51), scripts 866 KiB (18) and stylesheets 336 KiB (32). Under 2 MB keeps phones on slow connections fast.

3 images (224 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.

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

1 image has no alt text, which hurts accessibility and image search.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h1 → h4, h2 → h4 and h3 → h5), 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 18 characters: “Home Eng - Ingemat”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 5 <h1> headlines (“Engineering Solutions for the Automotive Sector”, “Innovation” and “Education”). One clear main headline is easier for people and search engines.

The homepage links to 61 pages on ingemat.com and 9 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.ingemat.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.ingemat.com/solutions/soluciones_propuestas.php has no <title>, so Google invents the link text in results.

https://www.ingemat.com/es/home and https://www.ingemat.com/de/heim all use the title “Home - Ingemat”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ingemat.com/es/home, https://www.ingemat.com/fr/accueil, https://www.ingemat.com/de/heim, https://www.ingemat.com/company, https://www.ingemat.com/company/history and https://www.ingemat.com/company/mission-vision-and-values and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ingemat.com/news and https://www.ingemat.com/solutions/soluciones_propuestas.php have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.ingemat.com/new/wp-content/uploads/elementor/google-fonts/css/roboto.css?ver=1…”.

4 images are served at too low a resolution for sharp phone screens.

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 241 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

Opening the homepage sets 1 cookie (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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.