abc15.com website review

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

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

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

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

cloudfront.net costs a phone 1.1 s of main-thread work and 432 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 37 (desktop: 35). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

brightspotcdn.com costs a phone 198 ms of main-thread work and 12.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 516 ms of main-thread work and 638 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 443 ms of main-thread work and 708 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 37 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.

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

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

Polyfills for old browsers add 51 KiB JavaScript that modern phones do not need. 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.

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 57.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

6 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-10, real Chrome visitors' tap response (inp) went from 131 ms to 131 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 15.8 MB in 407 requests on a phone: images 11.7 MB (122), scripts 3.2 MB (65) and fonts 406 KiB (4). Under 2 MB keeps phones on slow connections fast.

thumbnail8.png weighs 6.3 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example thumbnail8.png at 1,280 px wide, shown at 342 px. Resized copies would save about 2.3 MB.

2 images (6.4 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.

2 images further down the page (6.4 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 4.47 g of CO₂e: 536.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 dropdown has no label.

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

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

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

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

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.

Page should contain a level-one heading: 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.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 168 pages on abc15.com and 29 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.

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

/live, /news/local-news, /videos, /breaking-news-alerts, /weather/daily-forecast and /weather/hourly-forecast and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /news/national-news, whose canonical is /news/national. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/news/national-news, /weather/impact-earth and /weather/alerts have no <h1> headline, so visitors and search engines get no clear main topic.

/videos took over 3 s to send its HTML from our server.

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

19 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 (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

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

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

1 link to other sites is dead, for example https://channelstore.roku.com/details/82106/abc15 (404).

2 links go through two or more redirects, for example http://www.scripps.com/careers/find-a-job.

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.

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

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

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

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

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 4 mores (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.

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

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 58 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.