2.5 sec in total
47 ms
2.2 sec
294 ms
Click here to check amazing Statscity content. Otherwise, check out these important facts you probably never knew about statscity.com
Checkout the full domain details of Statscity.com. Click Buy Now to instantly start the transaction or Make an offer to the seller!
Visit statscity.comWe analyzed Statscity.com page load time and found that the first response time was 47 ms and then it took 2.5 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.
statscity.com performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value4.8 s
30/100
25%
Value3.3 s
90/100
10%
Value1,170 ms
21/100
30%
Value0.008
100/100
15%
Value9.6 s
29/100
10%
47 ms
114 ms
866 ms
74 ms
78 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Statscity.com, 76% (63 requests) were made to Cdn.sedo.com and 11% (9 requests) were made to Sedo.com. The less responsive or slowest element that took the longest time to load (866 ms) relates to the external source Sedo.com.
Page size can be reduced by 1.4 MB (67%)
2.1 MB
690.5 kB
In fact, the total size of Statscity.com main page is 2.1 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. 65% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 204.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 204.6 kB or 88% of the original size.
Potential reduce by 26.4 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. Statscity images are well optimized though.
Potential reduce by 774.2 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 774.2 kB or 71% of the original size.
Potential reduce by 386.4 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. Statscity.com needs all CSS files to be minified and compressed as it can save up to 386.4 kB or 83% of the original size.
Number of requests can be reduced by 56 (70%)
80
24
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Statscity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
statscity.com
47 ms
www.statscity.com
114 ms
details.php4
866 ms
jquery-ui.css
74 ms
gtld.buyers.css
78 ms
forms.css
87 ms
iehacks.css
89 ms
basic.css
79 ms
clickelements.css
90 ms
slide.css
92 ms
basemod_common.css
94 ms
basemod_layout0102.css
95 ms
content_correction.css
94 ms
content_common.css
102 ms
web_new.css
110 ms
contentstyle6.css
108 ms
navigation.css
104 ms
print_common.css
103 ms
magicsuggest.css
106 ms
tld-dialog.css
114 ms
base_additional.css
115 ms
tx_news_additional.css
111 ms
googlefonts.css
115 ms
font-awesome-4.css
115 ms
sedo.offerpage.css
113 ms
sedo.plusbox.css
116 ms
sedoDialogTip.css
115 ms
selectric.css
119 ms
jquery.js
117 ms
jquery-ui.js
134 ms
gtld.buyers.js
132 ms
modernizr.js
116 ms
etracker.js
133 ms
langselect.js
181 ms
selectbox.js
184 ms
core.js
183 ms
magicsuggest.js
184 ms
tld-dialog.js
186 ms
jquery.dialogTip.js
179 ms
font-awesome.min.css
101 ms
e.js
540 ms
override.css
128 ms
buttons.css
119 ms
forms.js
118 ms
jquery.thickbox.js
115 ms
jquery.getUrlParam.js
112 ms
jquery.timers-1.2.js
116 ms
jquery.dialogBox.js
117 ms
nNav.js
115 ms
slide.js
115 ms
functions.js
116 ms
swfobject.js
179 ms
navigation.js
103 ms
offerpage.js
104 ms
selectric.js
104 ms
bg_pagetop.gif
30 ms
gpt.js
39 ms
ga.js
36 ms
pubads_impl_82.js
29 ms
__utm.gif
28 ms
container.html
22 ms
jquery.js
367 ms
531 ms
t.js
562 ms
logo-sedo.png
20 ms
sprites.main.png
17 ms
Sedo-Logo.png
30 ms
sprites.buttons.png
14 ms
bg_contentbase.png
15 ms
BuyDomains_BrowseCategories_V2.jpg
197 ms
details.js
190 ms
sedo.sprites.offerpage.png
23 ms
sedo.sprites.png
25 ms
sedo.sprites.search.png
23 ms
secure-seals.png
22 ms
payment-options.png
23 ms
sprites.partner.logos.png
138 ms
common.php
210 ms
service.php
254 ms
yes.gif
5 ms
exclamation-mark.png
20 ms
domaining-com.gif
195 ms
loader.gif
260 ms
statscity.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
statscity.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
statscity.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 doesn't use legible font sizes
EN
US
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Statscity.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 Statscity.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.
statscity.com
Open Graph description is not detected on the main page of Statscity. 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: