7.5 sec in total
316 ms
7 sec
165 ms
Visit whattodo.com now to see the best up-to-date What To Do content and also check out these interesting facts you probably never knew about whattodo.com
What To Do.com the business hub for people and business!
Visit whattodo.comWe analyzed Whattodo.com page load time and found that the first response time was 316 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
whattodo.com performance score
name
value
score
weighting
Value13.9 s
0/100
10%
Value15.9 s
0/100
25%
Value21.1 s
0/100
10%
Value1,670 ms
11/100
30%
Value0.015
100/100
15%
Value23.6 s
1/100
10%
316 ms
5452 ms
418 ms
421 ms
504 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 78% of them (25 requests) were addressed to the original Whattodo.com, 16% (5 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Whattodo.com.
Page size can be reduced by 716.9 kB (77%)
932.8 kB
215.9 kB
In fact, the total size of Whattodo.com main page is 932.8 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 538.9 kB which makes up the majority of the site volume.
Potential reduce by 48.3 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 48.3 kB or 84% of the original size.
Potential reduce by 387.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 387.8 kB or 72% of the original size.
Potential reduce by 280.8 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. Whattodo.com needs all CSS files to be minified and compressed as it can save up to 280.8 kB or 83% of the original size.
Number of requests can be reduced by 22 (92%)
24
2
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What To Do. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
whattodo.com
316 ms
www.whattodo.com
5452 ms
jquery-ui-1.9.2.custom.css
418 ms
jquery.treeview.css
421 ms
theme.css
504 ms
geomaps.css
513 ms
jquery.min.js
83 ms
jquery-noconflict.js
90 ms
jquery-migrate.min.js
95 ms
caption.js
101 ms
head.load.min.js
194 ms
js
23 ms
bootstrap.css
114 ms
template.css
138 ms
css
30 ms
bootstrap.min.js
145 ms
template.min.js
80 ms
locale-en_GB.js
66 ms
jquery-ui-1.9.2.custom.min.js
347 ms
jquery.ui.datepicker-en-GB.js
122 ms
jreviews.js
338 ms
jquery.treeview.min.js
122 ms
hogan-3.0.2.min.js
122 ms
markerclusterer_packed.js
120 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
52 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
53 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
53 ms
EgBlzoNBIHxNPCMwXaAhYPesZW2xOQ-xsNqO47m55DA.ttf
54 ms
QABk9IxT-LFTJ_dQzv7xpJ0EAVxt0G0biEntp43Qt6E.ttf
52 ms
jrIcons.ttf
210 ms
jreviews.fields.js
178 ms
geomaps.js
267 ms
whattodo.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
whattodo.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
whattodo.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whattodo.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 Whattodo.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.
whattodo.com
Open Graph description is not detected on the main page of What To Do. 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: