sogenave.pt website review

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

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

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

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

Your mobile performance score is 29 (desktop: 51). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Polyfills for old browsers add 217 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

4 images could be 135 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

Google Tag Manager costs a phone 286 ms of main-thread work and 499 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 2.7 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Wistia costs a phone 227 ms of main-thread work and 346 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.

Google CDN costs a phone 67 ms of main-thread work and 348 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.

9 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.

6 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 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 4.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.90 (75th percentile). Good is under 0.1.

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

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

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

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

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

Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Fazemos a cobertura de todo o território nacional e trabalh…”. Most of its time is element render delay (10.0 s).

The layout shifts by 0.886 while loading, so content jumps under the reader's thumb. Good is under 0.1.

5 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 131 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.0 MB in 100 requests on a phone: media 5.3 MB (2), scripts 3.4 MB (43) and stylesheets 1.1 MB (10). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example mapa-distribuicao-sogenave.gif at 2,080 px wide, shown at 312 px. Resized copies would save about 60 KiB.

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

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

4 tap targets are too small or too close together to hit reliably with a finger.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

There are 2 <h1> headlines (“World of Food Solutions” and “Denúncia anónima”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Open Graph is missing og:description, so shared links fall back to guesses.

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

The homepage links to 62 pages on sogenave.pt and 19 external pages.

There is no https://www3.sogenave.pt/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://www3.sogenave.pt/certificados_apcer_sogenave-2 has no <title>, so Google invents the link text in results.

https://www3.sogenave.pt/contactos and https://www3.sogenave.pt/stage/contactos all use the title “Contactos - Sogenave”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www3.sogenave.pt/sobre, https://www3.sogenave.pt/solucoes, https://www3.sogenave.pt/solucoes/serdialvending, https://www3.sogenave.pt/contactos, https://www3.sogenave.pt/stage/contactos and https://www3.sogenave.pt/certificados_apcer_sogenave-2 have 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 https://www3.sogenave.pt/stage/contactos, whose canonical is https://www3.sogenave.pt/contactos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www3.sogenave.pt/certificados_apcer_sogenave-2 has no <h1> headline, so visitors and search engines get no clear main topic.

https://www3.sogenave.pt/sobre, https://www3.sogenave.pt/solucoes, https://www3.sogenave.pt/solucoes/cabazes-natal, https://www3.sogenave.pt/solucoes/food-equipment-2, https://www3.sogenave.pt/solucoes/serdialvending and https://www3.sogenave.pt/solucoes/suporte-a-eventos and 9 others took over 3 s to send their HTML from our server.

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

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

Your longest form asks for 9 fields (7 required). Every extra field lowers completion.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, LinkedIn Insight and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 5 cookies (measured from a US location before any click).

Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.