Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

Page Load Speed

6.9 sec in total

First Response

1.3 sec

Resources Loaded

5.3 sec

Page Rendered

290 ms

curiositycounts.org screenshot

About Website

Welcome to curiositycounts.org homepage info - get ready to check Curiositycounts best content right away, or after learning these important things about curiositycounts.org

Visit curiositycounts.org

Key Findings

We analyzed Curiositycounts.org page load time and found that the first response time was 1.3 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

curiositycounts.org 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.216

58/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

app.curiositycounts.org

1316 ms

GbGrXlb1_SVuhuSLBcdCXaJKfrI.js

28 ms

dashicons.min.css

2756 ms

theme-my-login.css

137 ms

h5p.css

156 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Curiositycounts.org, 10% (3 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Code.tidio.co. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source App.curiositycounts.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 290.4 kB (69%)

Content Size

419.8 kB

After Optimization

129.4 kB

In fact, the total size of Curiositycounts.org main page is 419.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. 40% of websites need less resources to load. Javascripts take 203.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 33.3 kB

  • Original 41.7 kB
  • After minification 41.7 kB
  • After compression 8.4 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 33.3 kB or 80% of the original size.

JavaScript Optimization

-65%

Potential reduce by 132.0 kB

  • Original 203.4 kB
  • After minification 170.6 kB
  • After compression 71.4 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 132.0 kB or 65% of the original size.

CSS Optimization

-72%

Potential reduce by 125.1 kB

  • Original 174.8 kB
  • After minification 142.0 kB
  • After compression 49.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. Curiositycounts.org needs all CSS files to be minified and compressed as it can save up to 125.1 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (83%)

Requests Now

24

After Optimization

4

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

Best Practices

curiositycounts.org 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

High

Page has valid source maps

SEO Factors

curiositycounts.org SEO score

50

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 Curiositycounts.org 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 Curiositycounts.org 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

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