Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

exeter.edu

Phillips Exeter Academy | Exeter

Page Load Speed

976 ms in total

First Response

187 ms

Resources Loaded

553 ms

Page Rendered

236 ms

exeter.edu screenshot

About Website

Click here to check amazing Exeter content for United States. Otherwise, check out these important facts you probably never knew about exeter.edu

Our Harkness approach to learning, based on discussion and student-centered teaching, pervades every aspect of life at Exeter, where goodness and knowledge go hand in hand.

Visit exeter.edu

Key Findings

We analyzed Exeter.edu page load time and found that the first response time was 187 ms and then it took 789 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

exeter.edu performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.588

11/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

exeter.edu

187 ms

styles.css

102 ms

styles-peamain.css

109 ms

mainnav.css

52 ms

font-awesome.css

5 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 92% of them (65 requests) were addressed to the original Exeter.edu, 4% (3 requests) were made to Calendar.exeter.edu and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (192 ms) belongs to the original domain Exeter.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 834.6 kB (52%)

Content Size

1.6 MB

After Optimization

767.5 kB

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

HTML Optimization

-74%

Potential reduce by 53.4 kB

  • Original 71.8 kB
  • After minification 59.9 kB
  • After compression 18.3 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 11.8 kB, which is 17% 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 53.4 kB or 74% of the original size.

Image Optimization

-11%

Potential reduce by 72.3 kB

  • Original 644.0 kB
  • After minification 571.7 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, Exeter needs image optimization as it can save up to 72.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-79%

Potential reduce by 580.2 kB

  • Original 733.3 kB
  • After minification 578.9 kB
  • After compression 153.1 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 580.2 kB or 79% of the original size.

CSS Optimization

-84%

Potential reduce by 128.6 kB

  • Original 153.0 kB
  • After minification 113.3 kB
  • After compression 24.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. Exeter.edu needs all CSS files to be minified and compressed as it can save up to 128.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (47%)

Requests Now

70

After Optimization

37

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

Accessibility Review

exeter.edu accessibility score

77

Accessibility Issues

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 [lang] attribute

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

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

exeter.edu 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

exeter.edu SEO score

77

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exeter.edu 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 Exeter.edu main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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