Tools & Wizards About Us

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

axess.stanford.edu

Stanford | Axess

Page Load Speed

3.2 sec in total

First Response

133 ms

Resources Loaded

2.9 sec

Page Rendered

149 ms

About Website

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

Visit axess.stanford.edu

Key Findings

We analyzed Axess.stanford.edu page load time and found that the first response time was 133 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

axess.stanford.edu performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

axess.stanford.edu

133 ms

axess.stanford.edu

267 ms

bootstrap-custom.css

564 ms

decanter.css

572 ms

decanter-custom.css

267 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 45% of them (10 requests) were addressed to the original Axess.stanford.edu, 27% (6 requests) were made to Fonts.gstatic.com and 23% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Axess.stanford.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (73%)

Content Size

1.4 MB

After Optimization

391.5 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Axess.stanford.edu main page is 1.4 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. 25% of websites need less resources to load. CSS take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 13.0 kB

  • Original 15.5 kB
  • After minification 9.9 kB
  • After compression 2.5 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 5.6 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 13.0 kB or 84% of the original size.

Image Optimization

-18%

Potential reduce by 57.1 kB

  • Original 321.8 kB
  • After minification 264.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, Axess Stanford needs image optimization as it can save up to 57.1 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-89%

Potential reduce by 987.1 kB

  • Original 1.1 MB
  • After minification 933.9 kB
  • After compression 124.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. Axess.stanford.edu needs all CSS files to be minified and compressed as it can save up to 987.1 kB or 89% of the original size.

Requests Breakdown

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

Requests Now

11

After Optimization

2

  • Images
  • CSS

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

Network Requests Diagram

Accessibility Review

axess.stanford.edu accessibility score

97

Accessibility Issues

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.

Best Practices

axess.stanford.edu best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

axess.stanford.edu SEO score

78

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

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 Axess.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 Axess.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 Axess 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: