Tools & Wizards About Us
pearweb.org screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

pearweb.org

PEAR - Social Emotional Assessments and Educator PD | Cambridge, MA

Page Load Speed

5.7 sec in total

First Response

1.7 sec

Resources Loaded

4 sec

Page Rendered

62 ms

pearweb.org screenshot

About Website

Welcome to pearweb.org homepage info - get ready to check PEAR Web best content for United States right away, or after learning these important things about pearweb.org

Partnerships in Education and Resilience (PEAR) provides trainings and assessment tools that inform educators about program quality and youth social-emotional development and academic engagement.

Visit pearweb.org

Key Findings

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

Performance Metrics

pearweb.org performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

pearweb.org

1680 ms

www.pearinc.org

80 ms

minified.js

41 ms

focus-within-polyfill.js

39 ms

polyfill.min.js

884 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Pearweb.org, 73% (19 requests) were made to Static.parastorage.com and 8% (2 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Pearweb.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 963.6 kB (67%)

Content Size

1.4 MB

After Optimization

473.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Pearweb.org main page is 1.4 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. 35% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 959.9 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 228.0 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 959.9 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 5.3 kB
  • After minification 5.3 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. PEAR Web images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.6 kB

  • Original 244.1 kB
  • After minification 244.1 kB
  • After compression 240.5 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 10 (59%)

Requests Now

17

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pearweb.org

pearweb.org

1680 ms

www.pearinc.org

www.pearinc.org

80 ms

minified.js

minified.js

41 ms

focus-within-polyfill.js

focus-within-polyfill.js

39 ms

polyfill.min.js

polyfill.min.js

884 ms

thunderbolt-commons.718dbdea.bundle.min.js

thunderbolt-commons.718dbdea.bundle.min.js

37 ms

main.a041a540.bundle.min.js

main.a041a540.bundle.min.js

40 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

43 ms

lodash.min.js

lodash.min.js

46 ms

react.production.min.js

react.production.min.js

45 ms

react-dom.production.min.js

react-dom.production.min.js

47 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

44 ms

Clover_notext.png

Clover_notext.png

90 ms

11062b_2c2966db42004be499668dff9cb6bd5f~mv2.jpg

11062b_2c2966db42004be499668dff9cb6bd5f~mv2.jpg

91 ms

bundle.min.js

bundle.min.js

53 ms

cca525a8-ad89-43ae-aced-bcb49fb271dc.woff

cca525a8-ad89-43ae-aced-bcb49fb271dc.woff

39 ms

09a4b57b-7400-4d30-b4ba-d6e303c57868.woff

09a4b57b-7400-4d30-b4ba-d6e303c57868.woff

38 ms

388ef902-2c31-4818-abb1-a40dcd81f6d6.woff

388ef902-2c31-4818-abb1-a40dcd81f6d6.woff

39 ms

bc176270-17fa-4c78-a343-9fe52824e501.woff

bc176270-17fa-4c78-a343-9fe52824e501.woff

38 ms

07d62b21-8d7a-4c36-be86-d32ab1089972.woff

07d62b21-8d7a-4c36-be86-d32ab1089972.woff

39 ms

a9e95a29-98a7-404a-90ee-1929ad09c696.woff

a9e95a29-98a7-404a-90ee-1929ad09c696.woff

39 ms

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

39 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

45 ms

deprecation-style.v5.css

deprecation-style.v5.css

25 ms

right-arrow.svg

right-arrow.svg

23 ms

Accessibility Review

pearweb.org accessibility score

90

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

Buttons do not have an accessible name

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

pearweb.org best practices score

92

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

Page has valid source maps

SEO Factors

pearweb.org SEO score

91

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

Links do not have descriptive text

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 Pearweb.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 Pearweb.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

pearweb.org

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