Tools & Wizards About Us
icechecker.com screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

icechecker.com

IceChecker

Page Load Speed

1.6 sec in total

First Response

32 ms

Resources Loaded

1.4 sec

Page Rendered

157 ms

icechecker.com screenshot

About Website

Visit icechecker.com now to see the best up-to-date Ice Checker content for United States and also check out these interesting facts you probably never knew about icechecker.com

Check the estimated thickness of the ice in a certain region. We use historic weather data to estimate ice growth

Visit icechecker.com

Key Findings

We analyzed Icechecker.com page load time and found that the first response time was 32 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

icechecker.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

icechecker.com

32 ms

icechecker.com

75 ms

css

44 ms

reset.css

19 ms

univers-else

1247 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 65% of them (11 requests) were addressed to the original Icechecker.com, 12% (2 requests) were made to Openfontlibrary.org and 6% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Openfontlibrary.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 96.7 kB (35%)

Content Size

275.8 kB

After Optimization

179.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Icechecker.com main page is 275.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. Only 10% of websites need less resources to load. Javascripts take 253.1 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 8.0 kB

  • Original 11.6 kB
  • After minification 11.4 kB
  • After compression 3.6 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 8.0 kB or 69% of the original size.

JavaScript Optimization

-32%

Potential reduce by 80.5 kB

  • Original 253.1 kB
  • After minification 216.7 kB
  • After compression 172.5 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 80.5 kB or 32% of the original size.

CSS Optimization

-73%

Potential reduce by 8.1 kB

  • Original 11.1 kB
  • After minification 8.5 kB
  • After compression 3.0 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. Icechecker.com needs all CSS files to be minified and compressed as it can save up to 8.1 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (82%)

Requests Now

11

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

icechecker.com

icechecker.com

32 ms

icechecker.com

icechecker.com

75 ms

css

css

44 ms

reset.css

reset.css

19 ms

univers-else

univers-else

1247 ms

sans-guilt-wafer

sans-guilt-wafer

1246 ms

onoff.css

onoff.css

30 ms

style.css

style.css

34 ms

style.css

style.css

32 ms

crickx.css

crickx.css

35 ms

modernizr.js

modernizr.js

50 ms

jquery.min.js

jquery.min.js

30 ms

countTo.js

countTo.js

32 ms

js

js

91 ms

analytics.js

analytics.js

20 ms

crickx-webfont.woff

crickx-webfont.woff

17 ms

icomoon.ttf

icomoon.ttf

11 ms

Accessibility Review

icechecker.com accessibility score

92

Accessibility Issues

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

SEO Factors

icechecker.com SEO score

92

Search Engine Optimization Advices

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Icechecker.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Icechecker.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

icechecker.com

Open Graph description is not detected on the main page of Ice Checker. 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: