7sealsinnovation.com website review

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

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

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

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

Reduce initial server response time. Google estimates savings of 607 ms on a phone.

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

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

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

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

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

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

Your server takes 707 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

2 third-party services load with your homepage (Vimeo and Google Fonts), adding 599 KiB and 88 ms of main-thread time.

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

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.

4 KiB could be saved by minifying CSS.

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

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

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

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

4 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 2.8 MB in 155 requests on a phone: images 1.1 MB (21), scripts 880 KiB (60) and fonts 393 KiB (13). Under 2 MB keeps phones on slow connections fast.

7 images (720 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.

2 images are downloaded at several times the size a phone draws them, for example SEVEN-SEALS_CLASSICS-PEATED-PORT.png at 896 px wide, shown at 238 px. Resized copies would save about 98 KiB.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

All page content should be contained by landmarks: 18 elements on the page fail 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.

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

Headings skip levels (h2 → h6), 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.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 40 pages on 7sealsinnovation.com and 30 external pages.

There is no https://7sealsinnovation.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://7sealsinnovation.com/en, https://7sealsinnovation.com/fr and https://7sealsinnovation.com/it declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

https://7sealsinnovation.com/en, https://7sealsinnovation.com/fr, https://7sealsinnovation.com/it, https://7sealsinnovation.com/seven-seals, https://7sealsinnovation.com/rumundo and https://7sealsinnovation.com/beavers-dram and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://7sealsinnovation.com/en, https://7sealsinnovation.com/fr, https://7sealsinnovation.com/it, https://7sealsinnovation.com/seven-seals, https://7sealsinnovation.com/rumundo and https://7sealsinnovation.com/beavers-dram and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://7sealsinnovation.com/impressum has 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.

https://7sealsinnovation.com/en, https://7sealsinnovation.com/fr, https://7sealsinnovation.com/it, https://7sealsinnovation.com/seven-seals, https://7sealsinnovation.com/rumundo and https://7sealsinnovation.com/beavers-dram and 2 others took over 3 s to send their HTML from our server.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://7sealsinnovation.com/.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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

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

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