2.6 sec in total
209 ms
2.2 sec
221 ms
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.comWe analyzed Ezy.com page load time and found that the first response time was 209 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
ezy.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value11.2 s
0/100
25%
Value8.9 s
15/100
10%
Value950 ms
29/100
30%
Value0.001
100/100
15%
Value12.3 s
15/100
10%
209 ms
665 ms
165 ms
167 ms
171 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ezy.com, 77% (57 requests) were made to Cdn.sedo.com and 9% (7 requests) were made to Sedo.com. The less responsive or slowest element that took the longest time to load (665 ms) relates to the external source Sedo.com.
Page size can be reduced by 1.3 MB (66%)
2.0 MB
664.9 kB
In fact, the total size of Ezy.com main page is 2.0 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 1.0 MB which makes up the majority of the site volume.
Potential reduce by 203.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. 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 203.9 kB or 88% of the original size.
Potential reduce by 24.8 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. Ezy images are well optimized though.
Potential reduce by 697.8 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 697.8 kB or 70% of the original size.
Potential reduce by 373.1 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 373.1 kB or 84% of the original size.
Number of requests can be reduced by 55 (76%)
72
17
The browser has sent 72 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 24 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
ezy.com
209 ms
auction_detail.php
665 ms
jquery-ui.css
165 ms
gtld.buyers.css
167 ms
forms.css
171 ms
iehacks.css
173 ms
basic.css
176 ms
clickelements.css
184 ms
slide.css
191 ms
basemod_common.css
191 ms
basemod_layout0102.css
189 ms
content_correction.css
192 ms
content_common.css
204 ms
web_new.css
207 ms
contentstyle6.css
216 ms
navigation.css
217 ms
print_common.css
217 ms
magicsuggest.css
218 ms
tld-dialog.css
231 ms
base_additional.css
232 ms
tx_news_additional.css
243 ms
googlefonts.css
240 ms
font-awesome-4.css
243 ms
sedoDialogTip.css
245 ms
jquery.js
285 ms
jquery-ui.js
343 ms
gtld.buyers.js
266 ms
modernizr.js
267 ms
etracker.js
268 ms
langselect.js
270 ms
selectbox.js
306 ms
core.js
305 ms
magicsuggest.js
306 ms
tld-dialog.js
305 ms
jquery.dialogTip.js
314 ms
forms.js
329 ms
jquery.getUrlParam.js
332 ms
jquery.thickbox.js
332 ms
font-awesome.min.css
22 ms
e.js
407 ms
override.css
178 ms
buttons.css
231 ms
cookie.js
231 ms
functions.js
226 ms
jquery.dialogBox.js
216 ms
bg_pagetop.gif
32 ms
gpt.js
47 ms
ga.js
169 ms
jquery.js
242 ms
560 ms
t.js
579 ms
logo-sedo.png
172 ms
BuyDomains_DomainAuctions_01.jpg
325 ms
currency.gif
358 ms
info.gif
417 ms
sprites.main.png
215 ms
Sedo-Logo.png
167 ms
sprites.buttons.png
166 ms
bg_contentbase.png
166 ms
bg_content100_head.gif
158 ms
bg_kasten7030.gif
185 ms
sedo.sprites.png
200 ms
pubads_impl_82.js
148 ms
fadebox_border_top.jpg
175 ms
fadebox_border_bottom.jpg
174 ms
secure-seals.png
175 ms
payment-options.png
195 ms
domaining-com.gif
304 ms
loader.gif
317 ms
sprites.partner.logos.png
100 ms
yes.gif
84 ms
exclamation-mark.png
83 ms
__utm.gif
32 ms
container.html
40 ms
ezy.com accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
ezy.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ezy.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
US
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 does not match 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.
ezy.com
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: