Tools & Wizards About Us

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

thrive.ly

Thrively - Strengths Assessments & Project-Based Learning for Students

Page Load Speed

1.8 sec in total

First Response

35 ms

Resources Loaded

1.5 sec

Page Rendered

244 ms

About Website

Click here to check amazing Thrive content. Otherwise, check out these important facts you probably never knew about thrive.ly

Discover students' unique strengths, interests, and aspirations to build the skills they need for success in the K-12 classroom and beyond.

Visit thrive.ly

Key Findings

We analyzed Thrive.ly page load time and found that the first response time was 35 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

thrive.ly performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.511

15/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

thrively.com

35 ms

www.thrively.com

258 ms

thrively-web-lander2.min.css

43 ms

home.svg

288 ms

menuIcon.svg

356 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Thrive.ly, 30% (10 requests) were made to Use.typekit.net and 12% (4 requests) were made to Static.thrively.com. The less responsive or slowest element that took the longest time to load (561 ms) relates to the external source Thrively.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.9 kB (4%)

Content Size

895.6 kB

After Optimization

857.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Thrive.ly main page is 895.6 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 672.8 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 37.8 kB

  • Original 57.2 kB
  • After minification 55.8 kB
  • After compression 19.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 37.8 kB or 66% of the original size.

JavaScript Optimization

-0%

Potential reduce by 97 B

  • Original 672.8 kB
  • After minification 672.8 kB
  • After compression 672.7 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

-0%

Potential reduce by 0 B

  • Original 165.6 kB
  • After minification 165.6 kB
  • After compression 165.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. Thrive.ly has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (41%)

Requests Now

22

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

thrive.ly accessibility score

53

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

thrive.ly best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

thrive.ly SEO score

85

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Thrive.ly 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 Thrive.ly 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 Thrive. 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: