1.2 sec in total
179 ms
959 ms
84 ms
Visit what.cd now to see the best up-to-date What content for United States and also check out these interesting facts you probably never knew about what.cd
Visit what.cdWe analyzed What.cd page load time and found that the first response time was 179 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
what.cd performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value3.5 s
64/100
25%
Value3.6 s
87/100
10%
Value220 ms
87/100
30%
Value0.082
94/100
15%
Value5.0 s
77/100
10%
179 ms
413 ms
337 ms
26 ms
332 ms
Our browser made a total of 10 requests to load all elements on the main page. We found that all of those requests were addressed to What.cd and no external sources were called. The less responsive or slowest element that took the longest time to load (413 ms) belongs to the original domain What.cd.
Page size can be reduced by 77.1 kB (63%)
122.0 kB
44.9 kB
In fact, the total size of What.cd main page is 122.0 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 113.7 kB which makes up the majority of the site volume.
Potential reduce by 1.1 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 1.1 kB or 54% of the original size.
Potential reduce by 26 B
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. What images are well optimized though.
Potential reduce by 75.0 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 75.0 kB or 66% of the original size.
Potential reduce by 1.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. What.cd needs all CSS files to be minified and compressed as it can save up to 1.0 kB or 63% of the original size.
Number of requests can be reduced by 5 (63%)
8
3
The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
what.cd
179 ms
what.cd
413 ms
style.css
337 ms
jquery.js
26 ms
script_start.js
332 ms
ajax.class.js
356 ms
cookie.class.js
333 ms
storage.class.js
356 ms
global.js
356 ms
logo.png
4 ms
what.cd 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
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
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.
what.cd 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
what.cd SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise What.cd can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that What.cd 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.
what.cd
Open Graph description is not detected on the main page of What. 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: