wthr.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: 217 ms

  217 ms

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

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

  +21%

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

• Page weight: 5.5 MB

  5.5 MB

  Your homepage downloads 5.5 MB on a phone, 1.5 MB of it images (26%). Under 2 MB keeps phones on slow connections fast.

• 12 images in older formats

  12 images (1.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.

  Elements (5)

• An image on the first screen is lazy-loaded

  c3857f46-cde7-4dd6-860e-1d508627c7e6_540x304.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  Elements (1)

• 1 image below the first screen load straight away

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

  Elements (1)

• About 1.6 g of CO₂ per visit

  1.57 g

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

• Hidden but focusable

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

  Elements (3)

• Malformed lists

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

  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)

• 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)

• 9 images without alt text

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

  Elements (2)

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

• ARIA role should be appropriate for the element (1 element)

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

  Elements (1)

• 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 (93 characters)

  Your title is 93 characters, so Google will cut it off around 60: “Indianapolis Local News: Weather, Traffic, Sports and more | Indianapolis, Indiana | wthr…”.

  View source

• 18 H1 headlines

  There are 18 <h1> headlines (“Indianapolis Local News: Weather, Traffic, Sports…”, “24/7 LIVE RADAR” and “Indiana state senator steps back from campaigning…”). One clear main headline is easier for people and search engines.

  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.

• 238 internal links, 131 external

  The homepage links to 238 pages on wthr.com and 131 external pages.

• Most text only appears after JavaScript runs

  17%

  A phone browser shows 1,575 words, but the HTML your server sends has only 263. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

• 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 101 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_FAILED”.

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

• Thin social proof

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

• 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,575 words of copy

  The homepage carries about 1,575 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.

• 30 cookies set on arrival

  30

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

• 77 other companies contacted

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