Tools & Wizards About Us
forecast.weather.gov screenshot

Report Summary

  • 77

    Performance

    Renders faster than
    85% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

forecast.weather.gov

National Weather Service

Page Load Speed

933 ms in total

First Response

72 ms

Resources Loaded

615 ms

Page Rendered

246 ms

forecast.weather.gov screenshot

About Website

Click here to check amazing Forecast Weather content for United States. Otherwise, check out these important facts you probably never knew about forecast.weather.gov

Visit forecast.weather.gov

Key Findings

We analyzed Forecast.weather.gov page load time and found that the first response time was 72 ms and then it took 861 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

forecast.weather.gov performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

38/100

25%

SI (Speed Index)

Value3.2 s

91/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

www.weather.gov

72 ms

weatherstyle.css

10 ms

template.css

14 ms

myfcst.css

11 ms

ForecastSearch.css

9 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Forecast.weather.gov, 87% (40 requests) were made to Weather.gov and 7% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (211 ms) relates to the external source Zn9tslis2mj3kopgp-cfigroup.siteintercept.qualtrics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 584.8 kB (55%)

Content Size

1.1 MB

After Optimization

485.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forecast.weather.gov main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 562.3 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 106.1 kB

  • Original 136.0 kB
  • After minification 114.7 kB
  • After compression 29.9 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. This page needs HTML code to be minified as it can gain 21.3 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 106.1 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 13.2 kB

  • Original 281.3 kB
  • After minification 268.0 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Forecast Weather images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 392.1 kB

  • Original 562.3 kB
  • After minification 512.7 kB
  • After compression 170.2 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 392.1 kB or 70% of the original size.

CSS Optimization

-81%

Potential reduce by 73.4 kB

  • Original 90.3 kB
  • After minification 71.7 kB
  • After compression 16.9 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. Forecast.weather.gov needs all CSS files to be minified and compressed as it can save up to 73.4 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

44

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.weather.gov

www.weather.gov

72 ms

weatherstyle.css

weatherstyle.css

10 ms

template.css

template.css

14 ms

myfcst.css

myfcst.css

11 ms

ForecastSearch.css

ForecastSearch.css

9 ms

pointforecast.css

pointforecast.css

11 ms

jquery-ui-1.10.3.custom.min.css

jquery-ui-1.10.3.custom.min.css

12 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

14 ms

jquery-ui-1.10.3.custom.min.js

jquery-ui-1.10.3.custom.min.js

18 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

12 ms

ForecastSearch.js

ForecastSearch.js

12 ms

federated-analytics.js

federated-analytics.js

14 ms

topNavMenu.js

topNavMenu.js

13 ms

NidsESRI.js

NidsESRI.js

13 ms

nwsexit.js

nwsexit.js

13 ms

foresee-trigger.js

foresee-trigger.js

16 ms

cfi.js

cfi.js

14 ms

jquery-cookie.js

jquery-cookie.js

14 ms

MyForecastWidget.js

MyForecastWidget.js

15 ms

wwamap.css

wwamap.css

15 ms

search.css

search.css

12 ms

ga.js

ga.js

73 ms

US.png

US.png

59 ms

hi.png

hi.png

180 ms

ak.png

ak.png

66 ms

bg.png

bg.png

10 ms

header.png

header.png

8 ms

header_doc.png

header_doc.png

9 ms

head_shadow.png

head_shadow.png

10 ms

myfcst-bg.png

myfcst-bg.png

11 ms

FloodSafety_TADD.png

FloodSafety_TADD.png

9 ms

HourlyWeatherGraph.png

HourlyWeatherGraph.png

11 ms

Winter_FeatureImage.png

Winter_FeatureImage.png

60 ms

twitter.png

twitter.png

59 ms

fb.png

fb.png

59 ms

youtube_play.png

youtube_play.png

60 ms

rss.png

rss.png

61 ms

bg_footer.png

bg_footer.png

60 ms

usa_gov.png

usa_gov.png

60 ms

myfcst-block-bg.png

myfcst-block-bg.png

61 ms

foresee-surveydef.js

foresee-surveydef.js

58 ms

__utm.gif

__utm.gif

22 ms

__utm.gif

__utm.gif

19 ms

foresee-dhtml.css

foresee-dhtml.css

6 ms

hi.png

hi.png

6 ms

211 ms

Accessibility Review

forecast.weather.gov accessibility score

71

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

High

Links do not have a discernible name

Best Practices

forecast.weather.gov best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

forecast.weather.gov SEO score

50

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forecast.weather.gov 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 Forecast.weather.gov main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

forecast.weather.gov

Open Graph description is not detected on the main page of Forecast Weather. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: