windytv.com Windy, Windyty. Wind map & weather forecast

Mobile Usability

96/100

Good

Mobile Speed

65/100

Medium

Last tested: 2017-08-29

Rescan
windytv.com Mobile Usability: 96/100
windytv.com Mobile Usability Test Quick Overview

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
The tap target <div id="overlay" class="noselect rh-it…or iconsize-14">|Wind7CloudsT…sPressureWind</div> and 1 others are close to other tap targets.
The tap target <div id="legend" class="metric-legend">kt051020304060</div> is close to 1 other tap targets.
The tap target <div id="mobile-menu" class="mobile-menu-switch fullscreen">Map Share Sear…Favorites Menu</div> and 3 others are close to other tap targets.
The tap target <div id="mobile-menu" class="mobile-menu-switch fullscreen">Map Share Sear…Favorites Menu</div> is close to 1 other tap targets.
The tap target <div id="mobile-menu" class="mobile-menu-switch fullscreen">Map Share Sear…Favorites Menu</div> is close to 1 other tap targets.
windytv.com Mobile Speed: 65/100
windytv.com Mobile Speed Test Quick Overview

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
https://www.windy.com/js/leaflet077_tileLayer.js
https://www.windy.com/v12.12/index.js
Optimize CSS Delivery of the following:
https://www.windy.com/v12.12/index.css
Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
Only about 2% of the final above-the-fold content could be rendered with the full HTML response.
Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 59.1KiB (37% reduction).
Compressing https://www.windy.com/img/covers/1.jpg could save 37.4KiB (34% reduction).
Compressing https://www.windy.com/ecmwf-hres/2017/08/29/06/257…surface.jpg?2017082812 could save 11KiB (44% reduction).
Compressing https://www.windy.com/ecmwf-hres/2017/08/29/06/257…surface.jpg?2017082812 could save 8.1KiB (43% reduction).
Compressing https://www.windy.com/img/icons2/png_27px/1.png could save 963B (49% reduction).
Compressing https://www.windy.com/img/icons2/png_27@2x/1.png could save 960B (50% reduction).
Compressing https://www.windy.com/img/icons2/png_27@2x/2.png could save 773B (39% reduction).
Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://www.google-analytics.com/analytics.js (2 hours)
https://www.windy.com/ecmwf-hres/2017/08/29/06/257…surface.jpg?2017082812 (5 hours)
https://www.windy.com/ecmwf-hres/2017/08/29/06/257…surface.jpg?2017082812 (5 hours)

windytv.com Mobile Resources


Total Resources51
Number of Hosts5
Static Resources35
JavaScript Resources7
CSS Resources1

windytv.com Mobile Resource Breakdown