Tools & Wizards About Us
rea.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

rea.com

REA | AP Test Prep | CLEP Test Prep | Teacher Certification Prep | College Admission Test Prep

Page Load Speed

857 ms in total

First Response

45 ms

Resources Loaded

698 ms

Page Rendered

114 ms

rea.com screenshot

About Website

Click here to check amazing REA content for United States. Otherwise, check out these important facts you probably never knew about rea.com

Focused test prep for AP

Visit rea.com

Key Findings

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

Performance Metrics

rea.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value260 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.327

35/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

rea.com

45 ms

www.rea.com

260 ms

global.css

3 ms

rea.css

5 ms

royalslider.css

6 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 72% of them (26 requests) were addressed to the original Rea.com, 6% (2 requests) were made to Ssl.google-analytics.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (260 ms) belongs to the original domain Rea.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (77%)

Content Size

2.7 MB

After Optimization

640.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rea.com main page is 2.7 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. 25% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 10.0 kB

  • Original 14.4 kB
  • After minification 13.5 kB
  • After compression 4.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 10.0 kB or 69% of the original size.

Image Optimization

-79%

Potential reduce by 1.9 MB

  • Original 2.4 MB
  • After minification 511.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. Obviously, REA needs image optimization as it can save up to 1.9 MB or 79% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 132.4 kB

  • Original 249.3 kB
  • After minification 248.4 kB
  • After compression 116.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 132.4 kB or 53% of the original size.

CSS Optimization

-77%

Potential reduce by 28.1 kB

  • Original 36.5 kB
  • After minification 31.9 kB
  • After compression 8.4 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. Rea.com needs all CSS files to be minified and compressed as it can save up to 28.1 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (38%)

Requests Now

34

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of REA. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

rea.com

rea.com

45 ms

www.rea.com

www.rea.com

260 ms

global.css

global.css

3 ms

rea.css

rea.css

5 ms

royalslider.css

royalslider.css

6 ms

rs-default-inverted.css

rs-default-inverted.css

11 ms

buttons.css

buttons.css

6 ms

conversion.js

conversion.js

90 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

19 ms

modernizr.js

modernizr.js

19 ms

jquery.royalslider.min.js

jquery.royalslider.min.js

20 ms

custom.js

custom.js

19 ms

header-logo.png

header-logo.png

20 ms

search-ico.png

search-ico.png

20 ms

ga.js

ga.js

24 ms

bbg.png

bbg.png

11 ms

AP_Slide.png

AP_Slide.png

12 ms

CLEP_Slide.png

CLEP_Slide.png

16 ms

TC_Slide.png

TC_Slide.png

10 ms

EMT_Slide.png

EMT_Slide.png

21 ms

CDL_Slide.png

CDL_Slide.png

20 ms

SS_Slide.png

SS_Slide.png

21 ms

footer-logo.png

footer-logo.png

11 ms

print.css

print.css

21 ms

__utm.gif

__utm.gif

11 ms

104 ms

dropshadow.png

dropshadow.png

86 ms

analytics.js

analytics.js

42 ms

footer-border.png

footer-border.png

7 ms

tabbg.gif

tabbg.gif

6 ms

tbg.png

tbg.png

6 ms

32 ms

collect

collect

13 ms

collect

collect

25 ms

js

js

57 ms

ga-audiences

ga-audiences

123 ms

Accessibility Review

rea.com accessibility score

43

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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.

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

rea.com best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

rea.com SEO score

54

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

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rea.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Rea.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

rea.com

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