Tools & Wizards About Us
hopes.stanford.edu screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

hopes.stanford.edu

HOPES: Huntington's Disease Outreach Project for Education at Stanford

Page Load Speed

6.1 sec in total

First Response

197 ms

Resources Loaded

5.7 sec

Page Rendered

214 ms

hopes.stanford.edu screenshot

About Website

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

HOPES is dedicated to making information about Huntington's disease more accessible to the average person. Learn more about HD today!

Visit hopes.stanford.edu

Key Findings

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

Performance Metrics

hopes.stanford.edu performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value27.2 s

0/100

10%

TBT (Total Blocking Time)

Value2,880 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.057

98/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

hopes.stanford.edu

197 ms

hopes.stanford.edu

2742 ms

wp-emoji-release.min.js

262 ms

flick.css

269 ms

hopes.stanford.edu

1939 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 93% of them (64 requests) were addressed to the original Hopes.stanford.edu, 4% (3 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Hopes.stanford.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (40%)

Content Size

2.9 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hopes.stanford.edu main page is 2.9 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 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 76.1 kB

  • Original 95.3 kB
  • After minification 87.7 kB
  • After compression 19.2 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 76.1 kB or 80% of the original size.

Image Optimization

-13%

Potential reduce by 212.9 kB

  • Original 1.6 MB
  • After minification 1.4 MB

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, HOPES Stanford needs image optimization as it can save up to 212.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 505.2 kB

  • Original 682.0 kB
  • After minification 602.7 kB
  • After compression 176.8 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 505.2 kB or 74% of the original size.

CSS Optimization

-81%

Potential reduce by 362.6 kB

  • Original 450.2 kB
  • After minification 389.2 kB
  • After compression 87.6 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. Hopes.stanford.edu needs all CSS files to be minified and compressed as it can save up to 362.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (81%)

Requests Now

62

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hopes.stanford.edu

hopes.stanford.edu

197 ms

hopes.stanford.edu

hopes.stanford.edu

2742 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

262 ms

flick.css

flick.css

269 ms

hopes.stanford.edu

hopes.stanford.edu

1939 ms

style.min.css

style.min.css

449 ms

classic-themes.min.css

classic-themes.min.css

207 ms

tooltip.css

tooltip.css

236 ms

dashicons.min.css

dashicons.min.css

310 ms

tooltips.min.css

tooltips.min.css

289 ms

ml-responsive-table.css

ml-responsive-table.css

296 ms

owl.carousel.min.css

owl.carousel.min.css

301 ms

psac-public.css

psac-public.css

355 ms

style.css

style.css

483 ms

css2

css2

27 ms

style.css

style.css

487 ms

media-queries.css

media-queries.css

376 ms

flexslider.css

flexslider.css

439 ms

jquery.ui.all.css

jquery.ui.all.css

440 ms

font-awesome.css

font-awesome.css

476 ms

prettyPhoto.css

prettyPhoto.css

505 ms

custom.css

custom.css

507 ms

style.css

style.css

542 ms

child-custom.css

child-custom.css

547 ms

jquery.min.js

jquery.min.js

673 ms

jquery-migrate.min.js

jquery-migrate.min.js

569 ms

scrollTo.js

scrollTo.js

572 ms

jquery.form.min.js

jquery.form.min.js

607 ms

mailchimp.js

mailchimp.js

612 ms

core.min.js

core.min.js

633 ms

datepicker.js

datepicker.js

697 ms

modernizr.min.js

modernizr.min.js

673 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

859 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

697 ms

tooltip.js

tooltip.js

737 ms

tooltip.min.js

tooltip.min.js

739 ms

tooltips.min.js

tooltips.min.js

763 ms

ml.responsive.table.min.js

ml.responsive.table.min.js

765 ms

swfobject.js

swfobject.js

639 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

627 ms

jquery.cycle2.min.js

jquery.cycle2.min.js

609 ms

jquery.validate.min.js

jquery.validate.min.js

605 ms

jquery.form.js

jquery.form.js

640 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

598 ms

custom.js

custom.js

603 ms

jquery.isotope.min.js

jquery.isotope.min.js

602 ms

datepicker.min.js

datepicker.min.js

619 ms

comment-reply.min.js

comment-reply.min.js

587 ms

hoverIntent.min.js

hoverIntent.min.js

574 ms

maxmegamenu.js

maxmegamenu.js

550 ms

jquery.ui.base.css

jquery.ui.base.css

526 ms

jquery.ui.theme.css

jquery.ui.theme.css

554 ms

jquery.ui.core.css

jquery.ui.core.css

68 ms

jquery.ui.datepicker.css

jquery.ui.datepicker.css

69 ms

HOPESwebsitelogo.png

HOPESwebsitelogo.png

137 ms

Listen-to-the-HOPES-Podcast-on-Spotify-Youtube-Amazon-and-more-1-1-e1701478695668.png

Listen-to-the-HOPES-Podcast-on-Spotify-Youtube-Amazon-and-more-1-1-e1701478695668.png

639 ms

Listen-to-the-HOPES-Podcast-on-Spotify-Youtube-Amazon-and-more-1.png

Listen-to-the-HOPES-Podcast-on-Spotify-Youtube-Amazon-and-more-1.png

944 ms

founders-day-graphic-3.png

founders-day-graphic-3.png

241 ms

220198952img1.jpeg

220198952img1.jpeg

108 ms

roche-draft-c1-scaled.jpg

roche-draft-c1-scaled.jpg

302 ms

li-bullet.png

li-bullet.png

167 ms

arrow.jpg

arrow.jpg

195 ms

footer-bullit.png

footer-bullit.png

239 ms

scroll-top.png

scroll-top.png

267 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

49 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

58 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

59 ms

wARDj0u

wARDj0u

29 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

303 ms

Accessibility Review

hopes.stanford.edu accessibility score

89

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

button, link, and menuitem elements do not have accessible names.

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

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

hopes.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

hopes.stanford.edu SEO score

86

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

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 Hopes.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 Hopes.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

hopes.stanford.edu

Open Graph data is detected on the main page of HOPES Stanford. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: