Tools & Wizards About Us
ccare.stanford.edu screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

ccare.stanford.edu

The Center for Compassion and Altruism Research and Education (CCARE)

Page Load Speed

1.7 sec in total

First Response

186 ms

Resources Loaded

1.3 sec

Page Rendered

275 ms

ccare.stanford.edu screenshot

About Website

Click here to check amazing CCARE Stanford content for United States. Otherwise, check out these important facts you probably never knew about ccare.stanford.edu

CCARE investigates methods for cultivating compassion and promoting altruism within individuals and society.

Visit ccare.stanford.edu

Key Findings

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

Performance Metrics

ccare.stanford.edu performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value5.7 s

50/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

ccare.stanford.edu

186 ms

ccare.stanford.edu

152 ms

style.css

60 ms

style.min.css

116 ms

mediaelementplayer-legacy.min.css

85 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 75% of them (80 requests) were addressed to the original Ccare.stanford.edu, 7% (7 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (343 ms) belongs to the original domain Ccare.stanford.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 432.1 kB (23%)

Content Size

1.9 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ccare.stanford.edu main page is 1.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 843.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 62.9 kB

  • Original 80.1 kB
  • After minification 76.2 kB
  • After compression 17.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 62.9 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 26.0 kB

  • Original 843.4 kB
  • After minification 817.4 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. CCARE Stanford images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 336.1 kB

  • Original 842.7 kB
  • After minification 842.1 kB
  • After compression 506.5 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 336.1 kB or 40% of the original size.

CSS Optimization

-7%

Potential reduce by 7.0 kB

  • Original 96.3 kB
  • After minification 96.2 kB
  • After compression 89.3 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. Ccare.stanford.edu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 68 (72%)

Requests Now

94

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ccare.stanford.edu

ccare.stanford.edu

186 ms

ccare.stanford.edu

ccare.stanford.edu

152 ms

style.css

style.css

60 ms

style.min.css

style.min.css

116 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

85 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

92 ms

views-frontend.css

views-frontend.css

93 ms

aiwp-public.css

aiwp-public.css

91 ms

style.css

style.css

90 ms

styles.css

styles.css

111 ms

style.css

style.css

121 ms

wpr-hamburger.css

wpr-hamburger.css

121 ms

wprmenu.css

wprmenu.css

123 ms

wpr-icons.css

wpr-icons.css

124 ms

main.css

main.css

139 ms

css

css

35 ms

dashicons.min.css

dashicons.min.css

169 ms

toolset_maps_fixes.css

toolset_maps_fixes.css

150 ms

genesis-overrides.css

genesis-overrides.css

152 ms

full-width.css

full-width.css

218 ms

toolset-common-es-frontend.js

toolset-common-es-frontend.js

221 ms

jquery.min.js

jquery.min.js

193 ms

jquery-migrate.min.js

jquery-migrate.min.js

182 ms

aiwp-public.js

aiwp-public.js

233 ms

hrf-script.js

hrf-script.js

221 ms

expand.js

expand.js

215 ms

modernizr.custom.js

modernizr.custom.js

235 ms

touchSwipe.js

touchSwipe.js

247 ms

wprmenu.js

wprmenu.js

247 ms

core.min.js

core.min.js

250 ms

menu.min.js

menu.min.js

254 ms

selectmenu.min.js

selectmenu.min.js

253 ms

tooltip.min.js

tooltip.min.js

249 ms

moment.min.js

moment.min.js

289 ms

main.js

main.js

338 ms

buttons.js

buttons.js

16 ms

shortcodes.css

shortcodes.css

293 ms

ctct-plugin-recaptcha-v2.min.js

ctct-plugin-recaptcha-v2.min.js

277 ms

api.js

api.js

40 ms

ctct-plugin-frontend.min.js

ctct-plugin-frontend.min.js

283 ms

index.js

index.js

282 ms

buttons.js

buttons.js

14 ms

css

css

17 ms

css

css

22 ms

css

css

23 ms

css

css

22 ms

index.js

index.js

251 ms

hoverIntent.min.js

hoverIntent.min.js

238 ms

superfish.min.js

superfish.min.js

229 ms

superfish.args.min.js

superfish.args.min.js

232 ms

skip-links.min.js

skip-links.min.js

233 ms

browsetag-2.js

browsetag-2.js

247 ms

datepicker.min.js

datepicker.min.js

343 ms

mouse.min.js

mouse.min.js

337 ms

slider.min.js

slider.min.js

334 ms

jquery.ui.touch-punch.js

jquery.ui.touch-punch.js

331 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

333 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

331 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

315 ms

underscore.min.js

underscore.min.js

303 ms

wp-util.min.js

wp-util.min.js

303 ms

backbone.min.js

backbone.min.js

286 ms

wp-playlist.min.js

wp-playlist.min.js

273 ms

views-frontend.js

views-frontend.js

264 ms

1.jpg

1.jpg

79 ms

1.jpg

1.jpg

77 ms

1.jpg

1.jpg

76 ms

CCARE-logo-4.png

CCARE-logo-4.png

78 ms

SOM-1.png

SOM-1.png

77 ms

LeeEskey-EVENTS-100x100.png

LeeEskey-EVENTS-100x100.png

79 ms

fall24overlay.jpg%22

fall24overlay.jpg%22

76 ms

bg-slice-2.jpg

bg-slice-2.jpg

78 ms

university-logo.png

university-logo.png

215 ms

upper-quotes.png

upper-quotes.png

215 ms

lower-quotes.png

lower-quotes.png

214 ms

manifesting.jpg

manifesting.jpg

168 ms

Mind-Magic-200.jpg

Mind-Magic-200.jpg

215 ms

PeterShannonPost.jpg

PeterShannonPost.jpg

292 ms

CatherineSchweikertAuthor.jpg

CatherineSchweikertAuthor.jpg

334 ms

Follow-CCARE-White-4-1.png

Follow-CCARE-White-4-1.png

214 ms

wARDj0u

wARDj0u

4 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

85 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

86 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

135 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

145 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

134 ms

OZpEg_xvsDZQL_LKIF7q4jP3w2j_.ttf

OZpEg_xvsDZQL_LKIF7q4jP3w2j_.ttf

146 ms

OZpbg_xvsDZQL_LKIF7q4jP_eE3vcKnd.ttf

OZpbg_xvsDZQL_LKIF7q4jP_eE3vcKnd.ttf

147 ms

follow_button.html

follow_button.html

245 ms

like.php

like.php

135 ms

compassion-educaion-heading-tabs-full.png

compassion-educaion-heading-tabs-full.png

198 ms

slider-bottom-bg-2.jpg

slider-bottom-bg-2.jpg

196 ms

box-3.png

box-3.png

196 ms

footer-bottom-2.jpg

footer-bottom-2.jpg

237 ms

footer-follow-us-bg-2.jpg

footer-follow-us-bg-2.jpg

236 ms

Twitter-icon-white-4.png

Twitter-icon-white-4.png

239 ms

Facebook-icon-white-4.png

Facebook-icon-white-4.png

240 ms

LinkedIn-icon-white-4.png

LinkedIn-icon-white-4.png

239 ms

YouTube-icon-white-4.png

YouTube-icon-white-4.png

250 ms

Instagram-icon-white-4.png

Instagram-icon-white-4.png

264 ms

recaptcha__en.js

recaptcha__en.js

100 ms

y-w6ncCxpsQ.js

y-w6ncCxpsQ.js

82 ms

FEppCFCt76d.png

FEppCFCt76d.png

72 ms

fall24overlay.jpg

fall24overlay.jpg

244 ms

y-w6ncCxpsQ.js

y-w6ncCxpsQ.js

8 ms

embeds

embeds

101 ms

Accessibility Review

ccare.stanford.edu accessibility score

88

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

ccare.stanford.edu best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ccare.stanford.edu SEO score

91

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

Image elements do not have [alt] attributes

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

ccare.stanford.edu

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