Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

ezy.com

CSGO Cases | CS:GO Skins | VGO Case | CS GO Case Opening

Page Load Speed

1.2 sec in total

First Response

112 ms

Resources Loaded

1 sec

Page Rendered

61 ms

About Website

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

Ezy CS GO case opening brings you the best VGO case, CSGO cases and skin upgrade in one Ezy place. Roll epic CS:GO Skins and win the inventory of your dreams.

Visit ezy.com

Key Findings

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

Performance Metrics

ezy.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

ezy.com

112 ms

ezy.com

292 ms

gtm.js

71 ms

css

47 ms

index.2299a81a.css

275 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 43% of them (6 requests) were addressed to the original Ezy.com, 7% (1 request) were made to Googletagmanager.com and 7% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (306 ms) belongs to the original domain Ezy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 90.9 kB (16%)

Content Size

560.0 kB

After Optimization

469.1 kB

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

HTML Optimization

-60%

Potential reduce by 2.7 kB

  • Original 4.5 kB
  • After minification 4.5 kB
  • After compression 1.8 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 2.7 kB or 60% of the original size.

JavaScript Optimization

-15%

Potential reduce by 77.2 kB

  • Original 508.7 kB
  • After minification 508.7 kB
  • After compression 431.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 77.2 kB or 15% of the original size.

CSS Optimization

-24%

Potential reduce by 11.0 kB

  • Original 46.7 kB
  • After minification 46.7 kB
  • After compression 35.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. Ezy.com needs all CSS files to be minified and compressed as it can save up to 11.0 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (60%)

Requests Now

10

After Optimization

4

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

Accessibility Review

ezy.com accessibility score

94

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

ezy.com SEO score

76

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

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