Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

wiki.carleton.edu

Dashboard - Carlpedia - Carleton College Wiki

Page Load Speed

2.6 sec in total

First Response

203 ms

Resources Loaded

2.2 sec

Page Rendered

161 ms

wiki.carleton.edu screenshot

About Website

Welcome to wiki.carleton.edu homepage info - get ready to check Wiki Carleton best content for United States right away, or after learning these important things about wiki.carleton.edu

Visit wiki.carleton.edu

Key Findings

We analyzed Wiki.carleton.edu page load time and found that the first response time was 203 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

wiki.carleton.edu performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value12.8 s

3/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.23

54/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

wiki.carleton.edu

203 ms

wiki.carleton.edu

346 ms

batch.css

407 ms

batch.css

156 ms

batch.css

112 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 75% of them (30 requests) were addressed to the original Wiki.carleton.edu, 25% (10 requests) were made to Carleton.edu. The less responsive or slowest element that took the longest time to load (870 ms) belongs to the original domain Wiki.carleton.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 33.2 kB (37%)

Content Size

90.3 kB

After Optimization

57.1 kB

In fact, the total size of Wiki.carleton.edu main page is 90.3 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. 20% of websites need less resources to load. Images take 66.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 18.9 kB

  • Original 23.5 kB
  • After minification 19.0 kB
  • After compression 4.6 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 4.5 kB, which is 19% 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 18.9 kB or 80% of the original size.

Image Optimization

-21%

Potential reduce by 13.9 kB

  • Original 66.0 kB
  • After minification 52.2 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, Wiki Carleton needs image optimization as it can save up to 13.9 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-58%

Potential reduce by 458 B

  • Original 793 B
  • After minification 542 B
  • After compression 335 B

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. Wiki.carleton.edu needs all CSS files to be minified and compressed as it can save up to 458 B or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (39%)

Requests Now

31

After Optimization

19

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

Accessibility Review

wiki.carleton.edu accessibility score

83

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-*] attributes do not match their roles

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 [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

Links do not have a discernible name

Best Practices

wiki.carleton.edu 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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

wiki.carleton.edu SEO score

58

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

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 Wiki.carleton.edu 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 Wiki.carleton.edu 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 Wiki Carleton. 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: