Tools & Wizards About Us
whattodo.info screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% 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

  • 92

    SEO

    Google-friendlier than
    74% of websites

whattodo.info

Plan your Family Vacations in Colorado Ski Country with WhatToDo

Page Load Speed

4.2 sec in total

First Response

577 ms

Resources Loaded

3.3 sec

Page Rendered

369 ms

whattodo.info screenshot

About Website

Click here to check amazing What To Do content for United States. Otherwise, check out these important facts you probably never knew about whattodo.info

Family vacations in Colorado ski country are better with WhatToDo. Start your Colorado vacation planning with us.

Visit whattodo.info

Key Findings

We analyzed Whattodo.info page load time and found that the first response time was 577 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

whattodo.info performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.04

99/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

whattodo.info

577 ms

www.whattodo.info

1343 ms

wp-emoji-release.min.js

38 ms

style.css

126 ms

css

37 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 41% of them (32 requests) were addressed to the original Whattodo.info, 10% (8 requests) were made to Fonts.gstatic.com and 9% (7 requests) were made to Cdn.whattodo.info. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Whattodo.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (8%)

Content Size

15.0 MB

After Optimization

13.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whattodo.info main page is 15.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. 70% of websites need less resources to load. Images take 13.9 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 50.8 kB

  • Original 66.4 kB
  • After minification 62.4 kB
  • After compression 15.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 50.8 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 336.1 kB

  • Original 13.9 MB
  • After minification 13.5 MB

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 To Do images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 373.2 kB

  • Original 585.7 kB
  • After minification 510.8 kB
  • After compression 212.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 373.2 kB or 64% of the original size.

CSS Optimization

-89%

Potential reduce by 412.2 kB

  • Original 465.2 kB
  • After minification 410.6 kB
  • After compression 53.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. Whattodo.info needs all CSS files to be minified and compressed as it can save up to 412.2 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (68%)

Requests Now

66

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 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 30 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

whattodo.info

whattodo.info

577 ms

www.whattodo.info

www.whattodo.info

1343 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

38 ms

style.css

style.css

126 ms

css

css

37 ms

css

css

52 ms

style.css

style.css

61 ms

shortcodes.css

shortcodes.css

64 ms

shortcodes_responsive.css

shortcodes_responsive.css

61 ms

magnific_popup.css

magnific_popup.css

62 ms

jquery.js

jquery.js

92 ms

jquery-migrate.min.js

jquery-migrate.min.js

88 ms

angular-material.min.css

angular-material.min.css

54 ms

icon

icon

72 ms

angular.min.js

angular.min.js

76 ms

angular-animate.min.js

angular-animate.min.js

72 ms

angular-aria.min.js

angular-aria.min.js

74 ms

angular-messages.min.js

angular-messages.min.js

75 ms

angular-material.min.js

angular-material.min.js

96 ms

typeahead.jquery.min.js

typeahead.jquery.min.js

86 ms

bloodhound.min.js

bloodhound.min.js

87 ms

handlebars.js

handlebars.js

111 ms

search_header.js

search_header.js

107 ms

adsbygoogle.js

adsbygoogle.js

7 ms

resorts_list.css

resorts_list.css

107 ms

frontend-builder-global-functions.js

frontend-builder-global-functions.js

109 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

114 ms

custom.js

custom.js

308 ms

jquery.fitvids.js

jquery.fitvids.js

307 ms

waypoints.min.js

waypoints.min.js

308 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

308 ms

frontend-builder-scripts.js

frontend-builder-scripts.js

309 ms

wp-embed.min.js

wp-embed.min.js

310 ms

logo.png

logo.png

236 ms

facebook.png

facebook.png

31 ms

twitter.png

twitter.png

29 ms

google_plus.png

google_plus.png

30 ms

linkedin.png

linkedin.png

32 ms

mail.png

mail.png

31 ms

Scuba_with_fish-1024x399.jpg

Scuba_with_fish-1024x399.jpg

375 ms

bigstock-winter-holidays-season-chris-103745507.jpg

bigstock-winter-holidays-season-chris-103745507.jpg

785 ms

ODelI1aHBYDBqgeIAH2zlEj2yz9RHX9Mk-2yzUB67_Y.ttf

ODelI1aHBYDBqgeIAH2zlEj2yz9RHX9Mk-2yzUB67_Y.ttf

46 ms

toadOcfmlt9b38dHJxOBGB5JIUTYQ8VE98d8HBeU5G4.ttf

toadOcfmlt9b38dHJxOBGB5JIUTYQ8VE98d8HBeU5G4.ttf

207 ms

toadOcfmlt9b38dHJxOBGCH-qnDt0uPJOZUUhznkTq0.ttf

toadOcfmlt9b38dHJxOBGCH-qnDt0uPJOZUUhznkTq0.ttf

262 ms

toadOcfmlt9b38dHJxOBGO2XAO3y59jwYldyr2GAzqM.ttf

toadOcfmlt9b38dHJxOBGO2XAO3y59jwYldyr2GAzqM.ttf

217 ms

toadOcfmlt9b38dHJxOBGAD27w_7GyaBwebaHTKWeA4.ttf

toadOcfmlt9b38dHJxOBGAD27w_7GyaBwebaHTKWeA4.ttf

262 ms

toadOcfmlt9b38dHJxOBGCtroqGasK-nicY6qOGcjLE.ttf

toadOcfmlt9b38dHJxOBGCtroqGasK-nicY6qOGcjLE.ttf

217 ms

ETmodules_v2_4.ttf

ETmodules_v2_4.ttf

312 ms

ca-pub-2576017107242212.js

ca-pub-2576017107242212.js

253 ms

zrt_lookup.html

zrt_lookup.html

248 ms

show_ads_impl.js

show_ads_impl.js

194 ms

2fcrYFNaTjcS6g4U3t-Y5bbKic1PW3nceB3q24YFOMg.ttf

2fcrYFNaTjcS6g4U3t-Y5bbKic1PW3nceB3q24YFOMg.ttf

320 ms

analytics.js

analytics.js

217 ms

geo_pages.json

geo_pages.json

142 ms

default_geo.json

default_geo.json

141 ms

default_geo_categories.json

default_geo_categories.json

119 ms

bigstock-Mountain-Bike-cyclist-riding-o-97231610.jpg

bigstock-Mountain-Bike-cyclist-riding-o-97231610.jpg

709 ms

Maroon-Bells.png

Maroon-Bells.png

579 ms

fishinggear_river-1140x445-1024x399.png

fishinggear_river-1140x445-1024x399.png

405 ms

crystal-mill.png

crystal-mill.png

692 ms

ads

ads

224 ms

osd.js

osd.js

45 ms

collect

collect

69 ms

collect

collect

68 ms

ads

ads

349 ms

css

css

15 ms

m_js_controller.js

m_js_controller.js

28 ms

abg.js

abg.js

40 ms

favicon

favicon

73 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

62 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

26 ms

s

s

38 ms

x_button_blue2.png

x_button_blue2.png

27 ms

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

5 ms

PuwvqkdbcqU-fCZ9Ed-b7cDdSZkkecOE1hvV7ZHvhyU.ttf

PuwvqkdbcqU-fCZ9Ed-b7cDdSZkkecOE1hvV7ZHvhyU.ttf

47 ms

favicon

favicon

57 ms

nr-852.min.js

nr-852.min.js

43 ms

ui

ui

34 ms

fd8cde79c6

fd8cde79c6

57 ms

Accessibility Review

whattodo.info accessibility score

94

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

whattodo.info 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

whattodo.info SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

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 Whattodo.info 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.info 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

whattodo.info

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: