sealed.com website review

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

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

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

About 138 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 760 ms faster on a phone.

About 46 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.

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

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

5 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Cloudflare and others), adding 232 KiB and 115 ms of main-thread time.

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

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

6 KiB could be saved by minifying CSS.

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

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

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

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

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

15 images have no width and height attributes, so the layout jumps as each one loads.

5 images weigh 5.4 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 6.2 MB in 48 requests on a phone: images 5.6 MB (26), fonts 266 KiB (6) and scripts 244 KiB (9). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example shutterstock_641035918-2.jpg at 1,000 px wide, shown at 263 px. Resized copies would save about 3.2 MB.

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

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

Your title is 68 characters, so Google will cut it off around 60: “Sealed | Upgrade your home with insulation, HVAC and smart home tech”.

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

Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 32 pages on sealed.com and 1 external page.

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.sealed.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.sealed.com/contractors, https://www.sealed.com/homeowner, https://www.sealed.com/in-the-news, https://www.sealed.com/energy-star, https://www.sealed.com/homes-sample-application and https://www.sealed.com/implementing-measured-modeled and 3 others use the same meta description. A description written for each page earns more clicks.

https://www.sealed.com/contractors, https://www.sealed.com/homeowner and https://www.sealed.com/programs have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 566 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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.