ogs.it website review

20 images could be 5.0 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.

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

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

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

The page has 1,893 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 110 KiB of JavaScript is downloaded but never used on this page.

1 long task block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.

1 third-party service load with your homepage (italia.it), adding 66 KiB and 16 ms of main-thread time.

Polyfills for old browsers add 9 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.

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

Your largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “tonni”. Most of its time is resource load delay (1.7 s).

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

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

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

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

Your homepage downloads 6.3 MB in 30 requests on a phone: images 5.9 MB (20), scripts 191 KiB (2) and fonts 102 KiB (3). Under 2 MB keeps phones on slow connections fast.

15 images are downloaded at several times the size a phone draws them, for example Boa Mambo.png at 1,200 px wide, shown at 314 px. Resized copies would save about 3.0 MB.

2 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

18 images (5.6 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.

OGS_header_1920x540_mari_oceani.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image further down the page (319 KiB) 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.77 g of CO₂e: 212.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Interactive controls must not be nested: 9 elements on the page fail this check, rated serious by axe-core.

2 elements hidden from screen readers can still receive keyboard focus.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h4), 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 79 characters, so Google will cut it off around 60: “Homepage | OGS | Istituto Nazionale di Oceanografia e di Geofisica Sperimentale”.

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

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

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

The homepage links to 176 pages on ogs.it and 27 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.ogs.it/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.ogs.it/user is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.ogs.it/it, https://www.ogs.it/it/node and https://www.ogs.it/en/node all use the title “Homepage | OGS | Istituto Nazionale di Oceanografia e di Geofisica Sp…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ogs.it/it/node, https://www.ogs.it/en/node and https://www.ogs.it/user have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ogs.it/it/visione-missione-e-valori, https://www.ogs.it/it/organizzazione, https://www.ogs.it/it/onorificenze and https://www.ogs.it/it/infrastrutture-di-ricerca-e-laboratori-oceanografici use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.ogs.it/it/node, whose canonical is https://www.ogs.it/it. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.ogs.it/user has no <h1> headline, so visitors and search engines get no clear main topic.

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

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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