Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

highwire.stanford.edu

Home - Highwire Press

Page Load Speed

1.5 sec in total

First Response

225 ms

Resources Loaded

939 ms

Page Rendered

332 ms

highwire.stanford.edu screenshot

About Website

Visit highwire.stanford.edu now to see the best up-to-date Highwire Stanford content for United States and also check out these interesting facts you probably never knew about highwire.stanford.edu

Our technology is in the service of knowledge. We provide the nexus where it is collected, certified, stored and shared.

Visit highwire.stanford.edu

Key Findings

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

Performance Metrics

highwire.stanford.edu performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.53

14/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

highwire.stanford.edu

225 ms

home.highwire.org

180 ms

css_J1bIduw1Jg9UglaWZErIHhEI0sRkJOcU_ZhflBd5xgk.css

140 ms

css_G8-qBIcAzonkPTT9CuydwwFsZG0cvxkIyf9e8DHEpv0.css

141 ms

css_z-xb7aJ8zUnJQlo6TKzUnAdGSdOeybvnsPSpPNLtXKs.css

142 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Highwire.stanford.edu, 60% (28 requests) were made to D15e7cwno0s5is.cloudfront.net and 28% (13 requests) were made to Home.highwire.org. The less responsive or slowest element that took the longest time to load (306 ms) relates to the external source Home.highwire.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 418.0 kB (36%)

Content Size

1.2 MB

After Optimization

754.7 kB

In fact, the total size of Highwire.stanford.edu main page is 1.2 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. 50% of websites need less resources to load. Images take 716.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 25.7 kB

  • Original 33.4 kB
  • After minification 30.6 kB
  • After compression 7.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. 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 25.7 kB or 77% of the original size.

Image Optimization

-11%

Potential reduce by 80.8 kB

  • Original 716.3 kB
  • After minification 635.6 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, Highwire Stanford needs image optimization as it can save up to 80.8 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

-67%

Potential reduce by 164.7 kB

  • Original 245.0 kB
  • After minification 221.0 kB
  • After compression 80.3 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 164.7 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 146.8 kB

  • Original 178.0 kB
  • After minification 176.7 kB
  • After compression 31.2 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. Highwire.stanford.edu needs all CSS files to be minified and compressed as it can save up to 146.8 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

45

After Optimization

33

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

Accessibility Review

highwire.stanford.edu accessibility score

83

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

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

highwire.stanford.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

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

highwire.stanford.edu SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    UTF-8

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