Tools & Wizards About Us
icury.com screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

icury.com

ICURY : The Icecat token for decentralized product content syndication. Join the ICURY project now and receive free tokens!

Page Load Speed

3.5 sec in total

First Response

204 ms

Resources Loaded

2.6 sec

Page Rendered

645 ms

icury.com screenshot

About Website

Visit icury.com now to see the best up-to-date ICURY content and also check out these interesting facts you probably never knew about icury.com

The Icecat token for decentralized product content syndication. Join the ICURY project now and receive free tokens!

Visit icury.com

Key Findings

We analyzed Icury.com page load time and found that the first response time was 204 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

icury.com performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

icury.com

204 ms

icury.com

377 ms

63ofx.css

380 ms

640p8.css

394 ms

640p8.js

20 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that all of those requests were addressed to Icury.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Icury.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.5 kB (2%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Icury.com main page is 1.7 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. 25% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 29.2 kB

  • Original 37.2 kB
  • After minification 35.7 kB
  • After compression 8.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 29.2 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 6.9 kB

  • Original 1.6 MB
  • After minification 1.6 MB

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. ICURY images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 691 B

  • Original 11.2 kB
  • After minification 11.2 kB
  • After compression 10.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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 707 B

  • Original 18.4 kB
  • After minification 18.4 kB
  • After compression 17.7 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. Icury.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (18%)

Requests Now

22

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ICURY. 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 as a result speed up the page load time.

Network Requests Diagram

icury.com

icury.com

204 ms

icury.com

icury.com

377 ms

63ofx.css

63ofx.css

380 ms

640p8.css

640p8.css

394 ms

640p8.js

640p8.js

20 ms

index.js

index.js

392 ms

index.js

index.js

426 ms

navigation.js

navigation.js

436 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

30 ms

logo-icury.png

logo-icury.png

380 ms

hero-bg.jpg

hero-bg.jpg

735 ms

cat-bg.png

cat-bg.png

412 ms

Icecat-PDS-downloads-2021_v3.jpg

Icecat-PDS-downloads-2021_v3.jpg

446 ms

price-table-bg.jpg

price-table-bg.jpg

649 ms

roadmap-diagram.jpg

roadmap-diagram.jpg

511 ms

numbers-bg.jpg

numbers-bg.jpg

940 ms

team-08.jpg

team-08.jpg

918 ms

team-07.jpg

team-07.jpg

919 ms

team-06.jpg

team-06.jpg

987 ms

team-03.jpg

team-03.jpg

1112 ms

team-04.jpg

team-04.jpg

1205 ms

team-group-01-e1554653678756.jpg

team-group-01-e1554653678756.jpg

1452 ms

team-group-02-e1554653663484.jpg

team-group-02-e1554653663484.jpg

1451 ms

icecat-logo-white.png

icecat-logo-white.png

1326 ms

GTEestiDisplay-Medium.woff

GTEestiDisplay-Medium.woff

1384 ms

ProximaNova-Bold.woff

ProximaNova-Bold.woff

1519 ms

ProximaNova-Regular.woff

ProximaNova-Regular.woff

1585 ms

Accessibility Review

icury.com accessibility score

95

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

icury.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

icury.com SEO score

97

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 uses legible font sizes

High

Tap targets are not sized appropriately

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

icury.com

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