weather.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 LCP: 3.9 s

  3.9 s

  Real visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

• Real-user INP: 250 ms

  250 ms

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

• Real-user CLS: 0.17

  0.17

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

• Real-user FCP: 2.6 s

  2.6 s

  Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

• Real-user TTFB: 1.4 s

  1.4 s

  Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

• Tap response (INP) held steady for real visitors

  -6%

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

• Largest content (LCP) held steady for real visitors

  -1%

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

• Page weight: 2.5 MB

  2.5 MB

  Your homepage downloads 2.5 MB on a phone, 11 KiB of it images (0%). Under 2 MB keeps phones on slow connections fast.

• About 0.7 g of CO₂ per visit

  0.70 g

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

• 7 text elements with low contrast

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

  Elements (3)

• 1 tap target too small

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

  Elements (1)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  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.

  Elements (1)

• 2 links without text

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

• No H1 headline

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

• Title is long (116 characters)

  Your title is 116 characters, so Google will cut it off around 60: “National and Local Weather Radar, Daily Forecast, Hurricane and information from The Weat…”.

  View source

• No social preview image

  No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  View source

• 58 internal links, 16 external

  The homepage links to 58 pages on weather.com and 16 external pages.

• Opted out of AI training for 1 crawler

  robots.txt blocks CCBot, 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.

• 4 pages point its canonical at the homepage

  /weather/today/l, /weather/radar/interactive/l, /redir and /weather/tenday/l declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  Elements (4)

• 5 pages share a title

  /, /weather/today/l, /weather/radar/interactive/l, /redir and /weather/tenday/l all use the title “National and Local Weather Radar, Daily Forecast, Hurricane and infor…”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (5)

• 4 pages share a meta description

  /weather/today/l, /weather/radar/interactive/l, /redir and /weather/tenday/l use the same meta description. A description written for each page earns more clicks.

• 4 pages without an H1

  /weather/today/l, /weather/radar/interactive/l, /redir and /weather/tenday/l have no <h1> headline, so visitors and search engines get no clear main topic.

• 8 pages with very little text

  /news/winter, /news/el-nino, /news/tornadoes, /news/health-and-wellness, /news/wildfires and /news/fall-outlook and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 38 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 “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.

• 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 analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

• Only about 114 words

  The homepage has only about 114 words of visible text; thin pages give Google and first-time buyers little to go on.

• No form on the homepage

  There is no form on the homepage, so every lead has to click through to another page first.

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

• 6 trackers load before any consent

  6

  Before a visitor clicks anything, the page loads Amazon Ads, Amplitude, Criteo, Google Ads and Taboola and 1 more (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.

• 19 cookies set on arrival

  19

  Opening the homepage sets 19 cookies (measured from a US location before any click).

• No consent tool detected

  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.

• 57 other companies contacted

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