abc10.com website review

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

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

5 images could be 703 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

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

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

Your mobile performance score is 26. 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 CDN, Google Tag Manager and Web Content Assessor and others), adding 3.5 MB and 3.5 s of main-thread time.

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

Google Tag Manager costs a phone 718 ms of main-thread work and 578 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.

Web Content Assessor costs a phone 493 ms of main-thread work and 145 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 192 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

Taboola costs a phone 399 ms of main-thread work and 650 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.

62 KiB could be saved by minifying JavaScript.

aditude.io costs a phone 328 ms of main-thread work and 265 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.

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

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

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

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.

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

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

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

The page becomes fully interactive after 61.5 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.

Real visitors wait 245 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

52 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' tap response (inp) went from 214 ms to 236 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.8 MB in 1,347 requests on a phone: scripts 5.1 MB (140), images 2.2 MB (343) and other files 965 KiB (722). Under 2 MB keeps phones on slow connections fast.

5 images (688 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.

1 image further down the page (324 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

Some list items are not inside a list.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 tap target is too small or too close together to hit reliably with a finger.

9 images have no alt text, which hurts accessibility and image search.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4, h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 103 characters, so Google will cut it off around 60: “Sacramento's Leading Local News: Weather, Traffic, Sports and more | Sacramento, Californ…”.

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

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

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:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 139 pages on abc10.com and 19 external pages.

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 /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.

/race-and-culture took over 3 s to send its HTML from our server.

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

30 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 (“The Topics API is deprecated and will be removed in a future release.”).

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

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

Your certificate from Let's Encrypt · YR2 expires in 13 days. If it doesn't renew automatically, visitors get a security warning.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 90 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

abc10.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

abc10.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

abc10.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

DMARC is set to p=none, so mail pretending to be abc10.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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