Website review, no card needed

weatherbug.com logo

weatherbug.com website review

Visit site (opens in a new tab)Reviewed 12 October 202622 issues · 78 checks

This review found 22 issues worth fixing on weatherbug.com, 6 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.4 sApr 18Oct 31.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.7 s
Apr 25, 20261.7 s
May 2, 20261.7 s
May 9, 20261.7 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.7 s
Jun 6, 20261.6 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
241 ms196 msApr 18Oct 3236 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026220 ms
Apr 25, 2026219 ms
May 2, 2026217 ms
May 9, 2026217 ms
May 16, 2026218 ms
May 23, 2026214 ms
May 30, 2026209 ms
Jun 6, 2026205 ms
Jun 13, 2026201 ms
Jun 20, 2026202 ms
Jun 27, 2026204 ms
Jul 4, 2026209 ms
Jul 11, 2026215 ms
Jul 18, 2026216 ms
Jul 25, 2026220 ms
Aug 1, 2026224 ms
Aug 8, 2026228 ms
Aug 15, 2026230 ms
Aug 22, 2026231 ms
Aug 29, 2026230 ms
Sep 5, 2026229 ms
Sep 12, 2026230 ms
Sep 19, 2026234 ms
Sep 26, 2026235 ms
Oct 3, 2026236 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of weatherbug.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. weatherbug.com at 0.4 s0.4 s
  2. weatherbug.com at 0.8 s0.8 s
  3. weatherbug.com at 1.1 s1.1 s
  4. weatherbug.com at 1.5 s1.5 s
  5. weatherbug.com at 1.9 s1.9 s
  6. weatherbug.com at 2.3 s2.3 s
  7. weatherbug.com at 2.6 s2.6 s
  8. weatherbug.com at 3.0 s3.0 s

Speed

3 to fix90
  • Use efficient cache lifetimes

    500 ms · 304 KiB

    57 files are served with short cache lifetimes, so returning visitors download them again (304 KiB).

  • Reduce unused JavaScript

    742 KiB

    About 742 KiB of JavaScript is downloaded but never used on this page.

  • sellwild.com adds 69 ms

    69 ms

    sellwild.com costs a phone 69 ms of main-thread work and 596 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (sellwild.com, LongTail Ad Solutions and weatherbug.net and others), adding 653 KiB and 89 ms of main-thread time.

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • 4 long tasks on the main thread

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

  • Improve image delivery

    33 KiB

    2 images could be 33 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90 (desktop: 93). That is in Google's “good” band (90 and up).

  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 722 ms of it running JavaScript. That is comfortably low.

  • Server response: 14 ms

    14 ms

    Your server sent the HTML in 14 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 12.7 s

    12.7 s

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

  • Real-user INP: 201 ms

    201 ms

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

    Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use technologies, such as cookies, to analyze your use (…”.

  • Tap response (INP) held steady for real visitors

    +7%

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

9 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 632 ms

    632 ms

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

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Total Blocking Time: 97 ms

    97 ms

    Scripts block the page for only 97 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Speed Index: 2.2 s

    2.2 s

    Visually, the page fills in at 2.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.54 g

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

4 checks passed
  • Page weight: 1.9 MB in 92 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 92 requests on a phone: scripts 1.5 MB (52), images 249 KiB (23) and other files 81 KiB (12). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9493
  • Links must have discernible text (2 elements)

    Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 tap target too small

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

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

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • 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 use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (1 element).

  • Frames without titles

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

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10097
  • No social preview image

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

  • 102 internal links, 13 external

    The homepage links to 102 pages on weatherbug.com and 13 external pages.

7 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “WeatherBug has current and extended local and national weather forecasts, live weather radar, news, temperature, lightn…”.

  • One H1 headline

    Your main headline reads: “Today's Weather”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Local & National Weather Forecasts - Weather Radar & News”.

  • Canonical URL set

    The canonical URL is https://www.weatherbug.com/.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.weatherbug.com/seo-sitemaps/usa-hour-sitemap-index.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (539 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 1 link), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 2 pages share a title

    /hurricane/active and /weather-videos/Extreme/20261011-Lightning-Zaps-Barcelona-Skyline all use the title “Warning”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 links to non-canonical URLs

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

  • 1 page with very little text

    /maps has 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 85 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 small tap targets

    4 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

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

  • No analytics detected

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

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

  • About 441 words of copy

    The homepage carries about 441 words of visible text.

1 checks passed
  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Comscore, Criteo, Google Ads, Google Tag Manager and The Trade Desk (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 27 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at weatherbug.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on weatherbug.com, including 7 speed issues, 1 SEO issue and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25