Tools & Wizards About Us
stormdisplay.weatherbug.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

stormdisplay.weatherbug.com

Local and National Weather Forecasts, Radar & News | WeatherBug

Page Load Speed

887 ms in total

First Response

12 ms

Resources Loaded

721 ms

Page Rendered

154 ms

stormdisplay.weatherbug.com screenshot

About Website

Visit stormdisplay.weatherbug.com now to see the best up-to-date Stormdisplay Weather Bug content for United States and also check out these interesting facts you probably never knew about stormdisplay.weatherbug.com

WeatherBug has current and extended local and national weather forecasts, news, temperature, live radar, lightning, hurricane alerts and more

Visit stormdisplay.weatherbug.com

Key Findings

We analyzed Stormdisplay.weatherbug.com page load time and found that the first response time was 12 ms and then it took 875 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

stormdisplay.weatherbug.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value3,580 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.212

59/100

15%

TTI (Time to Interactive)

Value25.4 s

0/100

10%

Network Requests Diagram

stormdisplay.weatherbug.com

12 ms

www.weatherbug.com

169 ms

styles.css

10 ms

init-32417zi2p5iizgqrts5k.js

241 ms

2K0cYisN.js

100 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Stormdisplay.weatherbug.com, 39% (7 requests) were made to Weatherbug.com and 11% (2 requests) were made to Api.fouanalytics.com. The less responsive or slowest element that took the longest time to load (281 ms) relates to the external source Ds.reson8.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 130.5 kB (17%)

Content Size

748.8 kB

After Optimization

618.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Stormdisplay.weatherbug.com main page is 748.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 555.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 122.3 kB

  • Original 155.3 kB
  • After minification 141.5 kB
  • After compression 33.0 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 122.3 kB or 79% of the original size.

JavaScript Optimization

-1%

Potential reduce by 7.0 kB

  • Original 555.7 kB
  • After minification 555.7 kB
  • After compression 548.7 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 1.2 kB

  • Original 37.7 kB
  • After minification 37.7 kB
  • After compression 36.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Stormdisplay.weatherbug.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (50%)

Requests Now

14

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stormdisplay Weather Bug. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

stormdisplay.weatherbug.com

stormdisplay.weatherbug.com

12 ms

www.weatherbug.com

www.weatherbug.com

169 ms

styles.css

styles.css

10 ms

init-32417zi2p5iizgqrts5k.js

init-32417zi2p5iizgqrts5k.js

241 ms

2K0cYisN.js

2K0cYisN.js

100 ms

main.21f120e9bd378734b6bd.js

main.21f120e9bd378734b6bd.js

101 ms

gtm.js

gtm.js

140 ms

lpvJm3_RkcS-vr_qgSHMbYB-jcbRkH2oNRB2URpg6t2W3jP_TPy9Na4D7qHs5MdytwG

lpvJm3_RkcS-vr_qgSHMbYB-jcbRkH2oNRB2URpg6t2W3jP_TPy9Na4D7qHs5MdytwG

125 ms

loader.js

loader.js

103 ms

analytics.min.js

analytics.min.js

133 ms

ui.svg

ui.svg

25 ms

logo.new.color.svg

logo.new.color.svg

67 ms

wb_logo_single.svg

wb_logo_single.svg

65 ms

responsive-menu-icon.svg

responsive-menu-icon.svg

62 ms

p

p

281 ms

i.js

i.js

262 ms

pp.js

pp.js

28 ms

aidem.js

aidem.js

262 ms

Accessibility Review

stormdisplay.weatherbug.com accessibility score

85

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

Best Practices

stormdisplay.weatherbug.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

stormdisplay.weatherbug.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stormdisplay.weatherbug.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Stormdisplay.weatherbug.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

stormdisplay.weatherbug.com

Open Graph data is detected on the main page of Stormdisplay Weather Bug. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: