martifer.com website review

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

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

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

7 long tasks block the main thread while loading, the longest for 240 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 81 KiB of JavaScript is downloaded but never used on this page.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 50 ms.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

Your largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We see each project as a new challenge and with our capacit…”.

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

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

6 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 4.6 MB in 69 requests on a phone: media 2.6 MB (2), images 1.3 MB (12) and scripts 424 KiB (40). Under 2 MB keeps phones on slow connections fast.

imagem-porto.jpg weighs 806 KiB. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example imagem-porto.jpg at 1,776 px wide, shown at 293 px. Resized copies would save about 932 KiB.

5 images (1.2 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.

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

SVG elements with an img role do not have an accessible text alternative (1 element).

Elements with visible text labels do not have matching accessible names. (4 elements).

Your title is only 8 characters: “Homepage”. 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.

There are 2 <h1> headlines (“Challenging limits every day” and “For over 36 years, Martifer has been developing s…”). 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.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

3 links have no real href, so search engines can't follow them.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 57 pages on martifer.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://martifer.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://martifer.com/en/business-areas, https://martifer.com/en/projects, https://martifer.com/en/investors, https://martifer.com/en/media, https://martifer.com/en/industries/metallic-constructions and https://martifer.com/en/contacts and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://martifer.com/en/investors, https://martifer.com/en/media, https://martifer.com/en/projects/nrp-sines, https://martifer.com/en/projects/edp-headquarters, https://martifer.com/en/projects/abi-bakr and https://martifer.com/en/projects/world-explorer and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://martifer.com/en/projects, https://martifer.com/en/investors, https://martifer.com/en/media, https://martifer.com/en/media/downloads, https://martifer.com/en/projects/nrp-sines and https://martifer.com/en/projects/edp-headquarters and 3 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 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.

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

3 errors were logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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.