scully.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, termly.io and Hubspot and others), adding 843 KiB and 411 ms of main-thread time.

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

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

About 80 KiB of CSS is downloaded but never applied on this page.

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.

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

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

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

Your largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Built on Safety, Driven by Innovatio…”.

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 84 ms to 90 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.1 MB in 103 requests on a phone: images 1.4 MB (22), scripts 1.3 MB (66) and fonts 317 KiB (5). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 9March2026_edit.jpg at 1,500 px wide, shown at 302 px. Resized copies would save about 256 KiB.

1 image (404 KiB) is 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.

By the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 104.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

All page content should be contained by landmarks: 37 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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

Your title is 67 characters, so Google will cut it off around 60: “Scully | Overfill Prevention, Grounding Verification, & Tank Gauges”.

There are 6 <h1> headlines (“Scully Celebrates 90 Years of Safety & Innovation”, “Scully Releases New Vapor Connect™ Kit” and “HazLoc Approved Mobile Truck Tester Kit & App”). One clear main headline is easier for people and search engines.

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

The homepage links to 164 pages on scully.com and 9 external pages.

There is no /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.

/es, /fr, /de, /pt, /products and /product-category/overfill-prevention-controllers and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/es, /fr, /de, /pt, /products and /product-category/overfill-prevention-controllers and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/es, /fr, /de, /pt, /products and /product-category/overfill-prevention-controllers and 6 others took over 3 s to send their HTML from our server.

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

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

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

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 link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

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

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