king5.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user INP: 222 ms

  222 ms

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

• Tap response (INP) got 25% slower for real visitors

  +25%

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

• Page weight: 12.2 MB

  12.2 MB

  Your homepage downloads 12.2 MB on a phone, 8.1 MB of it images (66%). Under 2 MB keeps phones on slow connections fast.

• 6 images over 500 KB

  6 images weigh 4.6 MB together. On a phone connection a single image that size takes seconds.

  Elements (5)

• 12 images far larger than shown

  3.9 MB

  12 images are downloaded at several times the size a phone draws them, for example d0fcd517-9aff-4ca5-8cf3-1da60151236a_1920x1080.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 3.9 MB.

  Elements (5)

• 21 images in older formats

  21 images (7.9 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.

  Elements (5)

• 15 images below the first screen load straight away

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

  Elements (5)

• About 3.5 g of CO₂ per visit

  3.47 g

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

• 1 button without a name

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

  Elements (1)

• Orphan list items

  Some list items are not inside a list.

  Elements (3)

• ARIA commands must have an accessible name (1 element)

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

  Elements (1)

• Malformed lists

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

  Elements (1)

• Scrollable region must have keyboard access (1 element)

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

  Elements (1)

• Positive tabindex

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

  Elements (1)

• 10 images without alt text

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

  View sourceElements (3)

• All page content should be contained by landmarks (1 element)

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

  Elements (1)

• 8 links without text

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

• 2 form fields without a label

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

  View source

• Headings skip levels

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

  View sourceElements (1)

• Title is long (97 characters)

  Your title is 97 characters, so Google will cut it off around 60: “Seattle's Leading Local News: Weather, Traffic, Sports and More | Seattle, Washington | k…”.

  View source

• No structured data

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

• Meta description is long (204 characters)

  Your meta description is 204 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• Open Graph partly set

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

  View source

• No X (Twitter) card tag

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

• 163 internal links, 7 external

  The homepage links to 163 pages on king5.com and 7 external pages.

• No Organization structured data

  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.

• No llms.txt

  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.

• 15 internal pages checked

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

• 4 JavaScript errors while loading

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

• No call to action on the first screen

  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 social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• No direct contact details

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

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• About 1,371 words of copy

  The homepage carries about 1,371 words of visible text.

• Urgency cues

  The page uses urgency cues (a countdown or limited-time wording).

• 12 trackers load before any consent

  12

  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.

• 29 cookies set on arrival

  29

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

• 74 other companies contacted

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