Tools & Wizards About Us
whatstoknow.com screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

whatstoknow.com

** This domain may be for sale **

Page Load Speed

1.8 sec in total

First Response

400 ms

Resources Loaded

1.2 sec

Page Rendered

160 ms

whatstoknow.com screenshot

About Website

Welcome to whatstoknow.com homepage info - get ready to check Whatstoknow best content right away, or after learning these important things about whatstoknow.com

This domain may be for sale

Visit whatstoknow.com

Key Findings

We analyzed Whatstoknow.com page load time and found that the first response time was 400 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

whatstoknow.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

www.whatstoknow.com

400 ms

wp-emoji-release.min.js

35 ms

785440a7_ai1ec_parsed_css.css

74 ms

grey_blocks.css

32 ms

dashicons.min.css

51 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 71% of them (17 requests) were addressed to the original Whatstoknow.com, 13% (3 requests) were made to Fonts.gstatic.com and 4% (1 request) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (400 ms) belongs to the original domain Whatstoknow.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 517.4 kB (55%)

Content Size

938.2 kB

After Optimization

420.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatstoknow.com main page is 938.2 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. 50% of websites need less resources to load. CSS take 499.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 11.1 kB

  • Original 15.7 kB
  • After minification 14.7 kB
  • After compression 4.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 11.1 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-69%

Potential reduce by 141.6 kB

  • Original 206.1 kB
  • After minification 196.6 kB
  • After compression 64.6 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 141.6 kB or 69% of the original size.

CSS Optimization

-73%

Potential reduce by 364.7 kB

  • Original 499.4 kB
  • After minification 472.3 kB
  • After compression 134.6 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. Whatstoknow.com needs all CSS files to be minified and compressed as it can save up to 364.7 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (80%)

Requests Now

20

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.whatstoknow.com

www.whatstoknow.com

400 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

35 ms

785440a7_ai1ec_parsed_css.css

785440a7_ai1ec_parsed_css.css

74 ms

grey_blocks.css

grey_blocks.css

32 ms

dashicons.min.css

dashicons.min.css

51 ms

cff-style.css

cff-style.css

35 ms

font-awesome.min.css

font-awesome.min.css

302 ms

all-skins.css

all-skins.css

41 ms

css

css

57 ms

style.css

style.css

58 ms

font-awesome.css

font-awesome.css

49 ms

jquery.js

jquery.js

58 ms

jquery-migrate.min.js

jquery-migrate.min.js

52 ms

cforms.js

cforms.js

48 ms

flowplayer.min.js

flowplayer.min.js

55 ms

cff-scripts.js

cff-scripts.js

54 ms

theme.js

theme.js

48 ms

wp-embed.min.js

wp-embed.min.js

47 ms

solid.png

solid.png

96 ms

all.js

all.js

267 ms

bg-hatch.gif

bg-hatch.gif

70 ms

Ur66QXTDfN1RjqAm41DRZZ0EAVxt0G0biEntp43Qt6E.ttf

Ur66QXTDfN1RjqAm41DRZZ0EAVxt0G0biEntp43Qt6E.ttf

66 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

68 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

68 ms

Accessibility Review

whatstoknow.com accessibility score

33

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

whatstoknow.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

whatstoknow.com SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatstoknow.com 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 Whatstoknow.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.

Social Sharing Optimization

whatstoknow.com

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