10tv.com website review

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

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

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

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

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

Your mobile performance score is 31. 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 Taboola and others), adding 3.8 MB and 3.7 s of main-thread time.

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

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

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

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

Rubicon Project costs a phone 346 ms of main-thread work and 91 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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 22.5 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 18.4 s (Speed Index). Good is under 3.4 s.

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

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

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

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

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

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

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

Your homepage downloads 8.5 MB in 1,304 requests on a phone: scripts 5.1 MB (136), images 1.9 MB (354) and other files 913 KiB (660). Under 2 MB keeps phones on slow connections fast.

6 images (1.1 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.

12 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example 3fda2983-4f85-4d19-8c2c-01d2dc746a5b_1920x1080.jpg at 1,920 px wide, shown at 370 px. Resized copies would save about 320 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 2.42 g of CO₂e: 290.5 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.

7 elements hidden from screen readers can still receive keyboard focus.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

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

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

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

Headings skip levels (h2 → h4, h1 → h4 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. (3 elements).

Your title is 92 characters, so Google will cut it off around 60: “Columbus' Leading Local News: Weather, Traffic, Sports and more in Columbus, Ohio | 10tv.…”.

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 155 pages on 10tv.com and 5 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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /boomtown, whose canonical is /columbus-ohio-fastest-growing-cities-us-boomtown. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

29 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: net::ERR_FAILED”.

13 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”).

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.

10tv.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.

10tv.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.

Social proof on the homepage: 2 trust badges. 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.

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

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

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 31 cookies, 1 of them by other companies (measured from a US location before any click).

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