Tools & Wizards About Us
guesswhat.site screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

guesswhat.site

地球探検記

Page Load Speed

4.1 sec in total

First Response

1.2 sec

Resources Loaded

2.7 sec

Page Rendered

190 ms

guesswhat.site screenshot

About Website

Click here to check amazing Guesswhat content. Otherwise, check out these important facts you probably never knew about guesswhat.site

やりたいことしかやらない大学生。旅・英語・留学すべての現実や感じたことを紹介します。

Visit guesswhat.site

Key Findings

We analyzed Guesswhat.site page load time and found that the first response time was 1.2 sec and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

guesswhat.site performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

guesswhat.site

1228 ms

style.min.css

514 ms

styles.css

349 ms

style.css

702 ms

keyframes.css

351 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 90% of them (27 requests) were addressed to the original Guesswhat.site, 3% (1 request) were made to Ajax.googleapis.com and 3% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Guesswhat.site.

Page Optimization Overview & Recommendations

Page size can be reduced by 247.1 kB (39%)

Content Size

634.9 kB

After Optimization

387.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Guesswhat.site main page is 634.9 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. 30% of websites need less resources to load. Images take 244.0 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 217.1 kB

  • Original 241.3 kB
  • After minification 239.4 kB
  • After compression 24.2 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 217.1 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 244.0 kB
  • After minification 244.0 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. Guesswhat images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 2.4 kB

  • Original 54.3 kB
  • After minification 54.0 kB
  • After compression 51.9 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.

CSS Optimization

-29%

Potential reduce by 27.6 kB

  • Original 95.3 kB
  • After minification 94.4 kB
  • After compression 67.7 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. Guesswhat.site needs all CSS files to be minified and compressed as it can save up to 27.6 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (81%)

Requests Now

27

After Optimization

5

  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Guesswhat. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

guesswhat.site

guesswhat.site

1228 ms

style.min.css

style.min.css

514 ms

styles.css

styles.css

349 ms

style.css

style.css

702 ms

keyframes.css

keyframes.css

351 ms

all.min.css

all.min.css

528 ms

fontawesome5.css

fontawesome5.css

352 ms

style.css

style.css

524 ms

style.css

style.css

717 ms

style.css

style.css

343 ms

keyframes.css

keyframes.css

342 ms

jquery.lazyloadxt.spinner.css

jquery.lazyloadxt.spinner.css

498 ms

a3_lazy_load.min.css

a3_lazy_load.min.css

529 ms

jquery.min.js

jquery.min.js

29 ms

jquery-migrate.min.js

jquery-migrate.min.js

34 ms

lazysizes.min.js

lazysizes.min.js

529 ms

index.js

index.js

528 ms

index.js

index.js

528 ms

stickyfill.min.js

stickyfill.min.js

667 ms

javascript.js

javascript.js

689 ms

javascript.js

javascript.js

689 ms

jquery.lazyloadxt.extra.min.js

jquery.lazyloadxt.extra.min.js

691 ms

jquery.lazyloadxt.srcset.min.js

jquery.lazyloadxt.srcset.min.js

693 ms

jquery.lazyloadxt.extend.js

jquery.lazyloadxt.extend.js

694 ms

lazyload-twitter.js

lazyload-twitter.js

931 ms

clipboard.min.js

clipboard.min.js

17 ms

S__457056260.jpg

S__457056260.jpg

880 ms

lazy_placeholder.gif

lazy_placeholder.gif

306 ms

loading.gif

loading.gif

307 ms

icomoon.woff

icomoon.woff

272 ms

Accessibility Review

guesswhat.site accessibility score

98

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.

Best Practices

guesswhat.site 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

guesswhat.site SEO score

97

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Guesswhat.site can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Guesswhat.site 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

guesswhat.site

Open Graph description is not detected on the main page of Guesswhat. 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: