Tools & Wizards About Us
whatshallwedo.co.uk screenshot

Report Summary

  • 27

    Performance

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

  • 98

    SEO

    Google-friendlier than
    92% of websites

whatshallwedo.co.uk

What Shall We Do? - The Amazing Random Idea Generator

Page Load Speed

2.6 sec in total

First Response

811 ms

Resources Loaded

1.6 sec

Page Rendered

165 ms

whatshallwedo.co.uk screenshot

About Website

Welcome to whatshallwedo.co.uk homepage info - get ready to check What Shall We Do best content right away, or after learning these important things about whatshallwedo.co.uk

Let the kids use our Random Idea Generator to decide what to do in the school holidays or at weekends. Click to be shown a random idea,and submit your own ideas that you'd like to see in the Gene...

Visit whatshallwedo.co.uk

Key Findings

We analyzed Whatshallwedo.co.uk page load time and found that the first response time was 811 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

whatshallwedo.co.uk performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value1,510 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

whatshallwedo.co.uk

811 ms

autoptimize_64cb8b6b60f7b717895ddec0e0468921.css

305 ms

css

20 ms

css

38 ms

css

39 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 36% of them (14 requests) were addressed to the original Whatshallwedo.co.uk, 44% (17 requests) were made to Fonts.gstatic.com and 10% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (811 ms) belongs to the original domain Whatshallwedo.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 209.8 kB (19%)

Content Size

1.1 MB

After Optimization

892.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Whatshallwedo.co.uk main page is 1.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. 50% of websites need less resources to load. Images take 690.3 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 110.9 kB

  • Original 168.4 kB
  • After minification 168.3 kB
  • After compression 57.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 110.9 kB or 66% of the original size.

Image Optimization

-12%

Potential reduce by 84.1 kB

  • Original 690.3 kB
  • After minification 606.2 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. Obviously, What Shall We Do needs image optimization as it can save up to 84.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-6%

Potential reduce by 14.9 kB

  • Original 243.7 kB
  • After minification 243.7 kB
  • After compression 228.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 12 (75%)

Requests Now

16

After Optimization

4

  • Images
  • JavaScript
  • CSS

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What Shall We 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 7 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

whatshallwedo.co.uk

whatshallwedo.co.uk

811 ms

autoptimize_64cb8b6b60f7b717895ddec0e0468921.css

autoptimize_64cb8b6b60f7b717895ddec0e0468921.css

305 ms

css

css

20 ms

css

css

38 ms

css

css

39 ms

autoptimize_single_a3fa5e0d1d3549a61eec91759074920b.css

autoptimize_single_a3fa5e0d1d3549a61eec91759074920b.css

156 ms

autoptimize_single_7df4e6eb6d680e8a81e8d97606eead10.css

autoptimize_single_7df4e6eb6d680e8a81e8d97606eead10.css

155 ms

css

css

33 ms

jquery.min.js

jquery.min.js

241 ms

adsbygoogle.js

adsbygoogle.js

45 ms

adsbygoogle.js

adsbygoogle.js

69 ms

lazysizes.min.js

lazysizes.min.js

157 ms

e-202448.js

e-202448.js

12 ms

autoptimize_c993b93fead6a1b514e6ebf70c266a2d.js

autoptimize_c993b93fead6a1b514e6ebf70c266a2d.js

231 ms

gtm.js

gtm.js

109 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

12 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

21 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

32 ms

fa-brands-400.woff

fa-brands-400.woff

162 ms

fa-brands-400.woff

fa-brands-400.woff

241 ms

fa-solid-900.woff

fa-solid-900.woff

157 ms

fa-regular-400.woff

fa-regular-400.woff

89 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

35 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

31 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

47 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

31 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

68 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

67 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

30 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

68 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

30 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

30 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

68 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

68 ms

fontello.woff

fontello.woff

83 ms

cropped-Untitled-design-10-6.png

cropped-Untitled-design-10-6.png

403 ms

cropped-What-Shall-We-Do_-5-13.png

cropped-What-Shall-We-Do_-5-13.png

153 ms

Accessibility Review

whatshallwedo.co.uk 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

whatshallwedo.co.uk 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

High

Page has valid source maps

SEO Factors

whatshallwedo.co.uk SEO score

98

Search Engine Optimization Advices

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 Whatshallwedo.co.uk 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 Whatshallwedo.co.uk 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

whatshallwedo.co.uk

Open Graph data is detected on the main page of What Shall We Do. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: