sunshine811.com website review

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

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

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

8 third-party services load with your homepage (Squarespace, Cookiebot and Accessibe Accessibility Overlay and others), adding 2.6 MB and 1.0 s of main-thread time.

5 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Squarespace costs a phone 583 ms of main-thread work and 1.2 MB 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.

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

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

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

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

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

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

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

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

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

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.

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

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

Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Scripts block taps and scrolling for 405 ms in total while the page loads. Good is under 200 ms.

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

Your homepage downloads 5.1 MB in 109 requests on a phone: scripts 2.6 MB (60), images 2.1 MB (9) and fonts 276 KiB (14). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

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

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

Your title is only 12 characters: “Sunshine 811”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 5 <h1> headlines (“| Dangers Hide Below During Hurricane Season | Le…”, “| Dangers Hide Below During Hurricane Season | Le…” and “Safe digging begins here.”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/602d468e3d9bab5833f…”.

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.

The homepage links to 137 pages on sunshine811.com and 21 external pages.

Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://sunshine811.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://sunshine811.com/calendar-1, https://sunshine811.com/portal3 and https://sunshine811.com/full-ite-access are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://sunshine811.com/homeowner-faq and https://sunshine811.com/faqs all use the title “FAQs — Sunshine 811”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sunshine811.com/calendar-1, https://sunshine811.com/portal3, https://sunshine811.com/homeowner-lp, https://sunshine811.com/homeowner-faq, https://sunshine811.com/6-steps-to-safe-digging and https://sunshine811.com/get-started-create-a-ticket and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://sunshine811.com/portal3 and https://sunshine811.com/full-ite-access have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of null (reading 'setAttribute')”.

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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