Report Summary

  • 67

    Performance

    Renders faster than
    80% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

wiki.washjeff.edu

Dashboard - Washington & Jefferson College Confluence

Page Load Speed

1 sec in total

First Response

107 ms

Resources Loaded

799 ms

Page Rendered

138 ms

wiki.washjeff.edu screenshot

About Website

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

Visit wiki.washjeff.edu

Key Findings

We analyzed Wiki.washjeff.edu page load time and found that the first response time was 107 ms and then it took 937 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

wiki.washjeff.edu performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

wiki.washjeff.edu

107 ms

batch.css

96 ms

batch.css

110 ms

default-theme.css

56 ms

batch.js

291 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 67% of them (20 requests) were addressed to the original Wiki.washjeff.edu, 17% (5 requests) were made to Fonts.gstatic.com and 10% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (417 ms) belongs to the original domain Wiki.washjeff.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 79.1 kB (70%)

Content Size

112.9 kB

After Optimization

33.8 kB

In fact, the total size of Wiki.washjeff.edu main page is 112.9 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. 35% of websites need less resources to load. HTML takes 60.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 47.1 kB

  • Original 60.0 kB
  • After minification 55.8 kB
  • After compression 12.8 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 47.1 kB or 79% of the original size.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.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 32.0 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (43%)

Requests Now

21

After Optimization

12

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

Accessibility Review

wiki.washjeff.edu accessibility score

80

Accessibility Issues

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

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

wiki.washjeff.edu best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wiki.washjeff.edu SEO score

91

Search Engine Optimization Advices

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

    N/A

  • 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.washjeff.edu can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Wiki.washjeff.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 Washjeff. 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: