sun-sentinel.com website review

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

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

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

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

Google Tag Manager costs a phone 1.0 s of main-thread work and 900 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Google/Doubleclick Ads and others), adding 4.0 MB and 4.5 s of main-thread time.

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

cloudfront.net costs a phone 881 ms of main-thread work and 79 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.

Google/Doubleclick Ads costs a phone 613 ms of main-thread work and 802 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.

Osano CMP costs a phone 509 ms of main-thread work and 121 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.

Ad Lightning costs a phone 483 ms of main-thread work and 201 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.

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

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

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

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

14 KiB could be saved by minifying JavaScript.

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

Your largest element takes 22.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Gov. Ron DeSantis is planning to run for president in 2028 …”.

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

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

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

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

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

For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.

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

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

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

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-31, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.1 MB in 1,141 requests on a phone: scripts 6.9 MB (197), images 2.5 MB (322) and other files 765 KiB (530). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example TFL-L-sun-sentinel-store-back-issues-folded.jpg at 2,491 px wide, shown at 148 px. Resized copies would save about 537 KiB.

16 images further down the page (974 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

10 images (416 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.

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

Images must have alternative text: 14 elements on the page fail this check, rated critical by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

Your title is 111 characters, so Google will cut it off around 60: “Sun Sentinel: Your source for South Florida breaking news, sports, business, entertainmen…”.

There are 2 <h1> headlines (“Sun Sentinel” and “”). One clear main headline is easier for people and search engines.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 247 pages on sun-sentinel.com and 55 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

There is no https://www.sun-sentinel.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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://www.sun-sentinel.com/newsletters has no <title>, so Google invents the link text in results.

https://www.sun-sentinel.com/util-clean-cookies, https://www.sun-sentinel.com/newsletters, https://www.sun-sentinel.com/location/florida/broward-county, https://www.sun-sentinel.com/location/florida/palm-beach-county and https://www.sun-sentinel.com/location/florida/miami-dade-county have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.sun-sentinel.com/util-clean-cookies, https://www.sun-sentinel.com/newsletters and https://www.sun-sentinel.com/weather have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sun-sentinel.com/util-clean-cookies 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.

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

4 images failed to load on a phone, for example https://rtb.mfadsrvr.com/sync?ssp=revcontent&ssp_user_id=5aff990073a244cb80bf8685af0aa0f4&gpp=DBACOe~CQtUCQAQtUCQAEX1iAENC3FgAAAAAEPgACiQAAAUlgIgAVAA4ACQAGgARQAmABoAEcAK0AZYBAACDgLzAaKA5YB8YFJQAAAA.IL.

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

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

Large scripts ship without source maps.

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

Requests the notification permission on page load.

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

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

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

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 1,785 words of visible text.

Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 3 mores (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 36 cookies, 2 of them by other companies (measured from a US location before any click).

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