Tools & Wizards About Us
prentice.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

prentice.com

K-12 Education Curriculum – K-12 Learning – Savvas Learning Company

Page Load Speed

2.1 sec in total

First Response

149 ms

Resources Loaded

1.2 sec

Page Rendered

776 ms

prentice.com screenshot

About Website

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

Savvas Learning Company creates award-winning K–12 education curriculum, assessments, and K-12 learning solutions to improve student outcomes.

Visit prentice.com

Key Findings

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

Performance Metrics

prentice.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.201

62/100

15%

TTI (Time to Interactive)

Value20.5 s

2/100

10%

Network Requests Diagram

prentice.com

149 ms

savvas.com

37 ms

www.savvas.com

140 ms

VisitorIdentification.js

20 ms

adrum-20.12.0.3360.js

15 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Prentice.com, 47% (15 requests) were made to Savvas-media-cdn.azureedge.net and 19% (6 requests) were made to Savvas-sc-content-hub-cdn.azureedge.net. The less responsive or slowest element that took the longest time to load (448 ms) relates to the external source Ssapi.savvas.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.1 kB (28%)

Content Size

923.0 kB

After Optimization

662.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prentice.com main page is 923.0 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. 55% of websites need less resources to load. Javascripts take 604.7 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 129.7 kB

  • Original 149.0 kB
  • After minification 94.6 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. This page needs HTML code to be minified as it can gain 54.4 kB, which is 36% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 129.7 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 8 B

  • Original 16.1 kB
  • After minification 16.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. Prentice images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 92.1 kB

  • Original 604.7 kB
  • After minification 604.7 kB
  • After compression 512.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 92.1 kB or 15% of the original size.

CSS Optimization

-25%

Potential reduce by 38.3 kB

  • Original 153.1 kB
  • After minification 153.1 kB
  • After compression 114.8 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. Prentice.com needs all CSS files to be minified and compressed as it can save up to 38.3 kB or 25% of the original size.

Requests Breakdown

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

Requests Now

26

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prentice. 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

prentice.com

prentice.com

149 ms

savvas.com

savvas.com

37 ms

www.savvas.com

www.savvas.com

140 ms

VisitorIdentification.js

VisitorIdentification.js

20 ms

adrum-20.12.0.3360.js

adrum-20.12.0.3360.js

15 ms

optimized-min.css

optimized-min.css

91 ms

optimized-min.css

optimized-min.css

107 ms

optimized-min.css

optimized-min.css

113 ms

pre-optimized-min.css

pre-optimized-min.css

121 ms

optimized-min.js

optimized-min.js

183 ms

optimized-min.js

optimized-min.js

97 ms

optimized-min.js

optimized-min.js

109 ms

optimized-min.js

optimized-min.js

110 ms

optimized-min.js

optimized-min.js

112 ms

optimized-min.js

optimized-min.js

397 ms

workers.js

workers.js

69 ms

xfvwkytd.js

xfvwkytd.js

448 ms

image-loading

image-loading

96 ms

3b9e9f735f674db6a6a135cfdce3bd2b

3b9e9f735f674db6a6a135cfdce3bd2b

118 ms

053dcf076c6f4adab57e251160a06121

053dcf076c6f4adab57e251160a06121

338 ms

da328281922744a09dd6fe1691b0ff2a

da328281922744a09dd6fe1691b0ff2a

339 ms

5a2e58b75a1e43bba3993ed6d0fda383

5a2e58b75a1e43bba3993ed6d0fda383

337 ms

1b83bacf4f3e470f976786b6706f77e3

1b83bacf4f3e470f976786b6706f77e3

340 ms

backdrop.png

backdrop.png

118 ms

404-page-not-found

404-page-not-found

111 ms

css2

css2

287 ms

css2

css2

288 ms

section-angle.svg

section-angle.svg

201 ms

dropdown-arrow.svg

dropdown-arrow.svg

197 ms

404-page-not-found

404-page-not-found

179 ms

font

font

120 ms

icomoon-ttf.ttf

icomoon-ttf.ttf

120 ms

Accessibility Review

prentice.com accessibility score

82

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Links do not have a discernible 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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 valid value for its [lang] attribute.

Best Practices

prentice.com best practices score

67

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

Displays images with incorrect aspect ratio

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

prentice.com SEO score

93

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

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

    N/A

  • Encoding

    UTF-8

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

prentice.com

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