Tools & Wizards About Us
images.capitolcorridor.org screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

images.capitolcorridor.org

Capitol Corridor Bay Area & N. California Rail Transportation

Page Load Speed

1.9 sec in total

First Response

27 ms

Resources Loaded

1.7 sec

Page Rendered

216 ms

images.capitolcorridor.org screenshot

About Website

Welcome to images.capitolcorridor.org homepage info - get ready to check Images Capitol Corridor best content for United States right away, or after learning these important things about images.capitolcorridor.org

Capitol Corridor is an intercity passenger rail service that operates between Silicon Valley/San Jose and the Sacramento region. Commute or explore with us.

Visit images.capitolcorridor.org

Key Findings

We analyzed Images.capitolcorridor.org page load time and found that the first response time was 27 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

images.capitolcorridor.org performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.164

72/100

15%

TTI (Time to Interactive)

Value27.0 s

0/100

10%

Network Requests Diagram

images.capitolcorridor.org

27 ms

www.capitolcorridor.org

48 ms

style.min.css

12 ms

css

56 ms

flik-timeline.min.css

22 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Images.capitolcorridor.org, 79% (78 requests) were made to Capitolcorridor.org and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (359 ms) relates to the external source Content.amtrak.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (28%)

Content Size

4.7 MB

After Optimization

3.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Images.capitolcorridor.org main page is 4.7 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. 80% 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 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 142.8 kB

  • Original 174.9 kB
  • After minification 169.3 kB
  • After compression 32.1 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 142.8 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 35.9 kB

  • Original 2.8 MB
  • After minification 2.7 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. Images Capitol Corridor images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 471.6 kB

  • Original 913.6 kB
  • After minification 903.1 kB
  • After compression 442.0 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 471.6 kB or 52% of the original size.

CSS Optimization

-84%

Potential reduce by 684.5 kB

  • Original 816.8 kB
  • After minification 802.6 kB
  • After compression 132.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. Images.capitolcorridor.org needs all CSS files to be minified and compressed as it can save up to 684.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (75%)

Requests Now

88

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

images.capitolcorridor.org

images.capitolcorridor.org

27 ms

www.capitolcorridor.org

www.capitolcorridor.org

48 ms

style.min.css

style.min.css

12 ms

css

css

56 ms

flik-timeline.min.css

flik-timeline.min.css

22 ms

magnific-popup.min.css

magnific-popup.min.css

17 ms

jquery.bxslider.min.css

jquery.bxslider.min.css

17 ms

font-awesome.min.css

font-awesome.min.css

21 ms

wpa-style.css

wpa-style.css

18 ms

nice-select.css

nice-select.css

21 ms

developer.css

developer.css

25 ms

integrity-light.css

integrity-light.css

41 ms

style.css

style.css

28 ms

tablepress-combined.min.css

tablepress-combined.min.css

23 ms

formreset.min.css

formreset.min.css

24 ms

formsmain.min.css

formsmain.min.css

29 ms

readyclass.min.css

readyclass.min.css

32 ms

browsers.min.css

browsers.min.css

33 ms

pum-site-styles.css

pum-site-styles.css

48 ms

ubermenu.min.css

ubermenu.min.css

35 ms

all.min.css

all.min.css

37 ms

fontello.css

fontello.css

46 ms

font-awesome.min.css

font-awesome.min.css

48 ms

style.css

style.css

48 ms

jquery.min.js

jquery.min.js

59 ms

jquery-migrate.min.js

jquery-migrate.min.js

48 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

48 ms

jquery.overscroll.min.js

jquery.overscroll.min.js

48 ms

flik-timeline.js

flik-timeline.js

49 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

59 ms

home1.js

home1.js

59 ms

jquery.json.min.js

jquery.json.min.js

60 ms

gravityforms.min.js

gravityforms.min.js

62 ms

api.js

api.js

70 ms

utils.min.js

utils.min.js

62 ms

fingerprint.min.js

fingerprint.min.js

59 ms

MyFontsWebfontsKit.css

MyFontsWebfontsKit.css

60 ms

cds_farefinder-core.css

cds_farefinder-core.css

59 ms

core.min.js

core.min.js

59 ms

jquery-ui-effects.js

jquery-ui-effects.js

60 ms

jquery-cycle.min.js

jquery-cycle.min.js

56 ms

cs-classic.7.5.6.js

cs-classic.7.5.6.js

55 ms

service_alerts.js

service_alerts.js

52 ms

faq.js

faq.js

51 ms

capcor.js

capcor.js

49 ms

search_box.js

search_box.js

48 ms

jquery.nice-select.js

jquery.nice-select.js

48 ms

x.js

x.js

47 ms

comment-reply.min.js

comment-reply.min.js

45 ms

dom-ready.min.js

dom-ready.min.js

42 ms

hooks.min.js

hooks.min.js

40 ms

i18n.min.js

i18n.min.js

40 ms

a11y.min.js

a11y.min.js

38 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

38 ms

vendor-theme.min.js

vendor-theme.min.js

36 ms

scripts-theme.min.js

scripts-theme.min.js

26 ms

pum-site-scripts.js

pum-site-scripts.js

27 ms

css

css

31 ms

ubermenu.min.js

ubermenu.min.js

24 ms

longdesc.min.js

longdesc.min.js

24 ms

wp-accessibility.min.js

wp-accessibility.min.js

25 ms

ajax.js

ajax.js

25 ms

css2

css2

19 ms

gtm.js

gtm.js

320 ms

fbevents.js

fbevents.js

248 ms

analytics.js

analytics.js

274 ms

events.js

events.js

247 ms

cap-corridor-logo-r.png

cap-corridor-logo-r.png

182 ms

calendar.png

calendar.png

359 ms

recaptcha__en.js

recaptcha__en.js

324 ms

CapCor_2021_Contactless_Masks_Homepage-Lg-1-1024x439.png

CapCor_2021_Contactless_Masks_Homepage-Lg-1-1024x439.png

170 ms

Pets--150x150.jpeg

Pets--150x150.jpeg

229 ms

friends-and-family_promo_sidebar-150x150.jpg

friends-and-family_promo_sidebar-150x150.jpg

170 ms

big-icon-train.png

big-icon-train.png

169 ms

big-icon-bus.png

big-icon-bus.png

169 ms

Routemap-homepage.jpg

Routemap-homepage.jpg

169 ms

30-percent-discount-homepage-large.jpg

30-percent-discount-homepage-large.jpg

201 ms

Health-Safety-Homepage.jpg

Health-Safety-Homepage.jpg

213 ms

friends-and-family_promo_sidebar.jpg

friends-and-family_promo_sidebar.jpg

201 ms

First-Time-Rider_551x552-2.jpg

First-Time-Rider_551x552-2.jpg

228 ms

levis-stadium-with-r.jpg

levis-stadium-with-r.jpg

214 ms

Pets-On-Board.jpeg

Pets-On-Board.jpeg

297 ms

10Rides_Social.jpg

10Rides_Social.jpg

229 ms

Levis-Stadium-Train-Banner-copy.jpg

Levis-Stadium-Train-Banner-copy.jpg

245 ms

Cafe_Care_Menu_Homepage_Promo.jpeg

Cafe_Care_Menu_Homepage_Promo.jpeg

243 ms

306B76_5_0.woff

306B76_5_0.woff

242 ms

cds.js

cds.js

270 ms

cds.js

cds.js

269 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

138 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

140 ms

fa-solid-900.ttf

fa-solid-900.ttf

193 ms

S6u9w4BMUTPHh6UVSwaPHA.ttf

S6u9w4BMUTPHh6UVSwaPHA.ttf

138 ms

S6uyw4BMUTPHjxAwWw.ttf

S6uyw4BMUTPHjxAwWw.ttf

190 ms

S6u9w4BMUTPHh7USSwaPHA.ttf

S6u9w4BMUTPHh7USSwaPHA.ttf

192 ms

306B76_2_0.woff

306B76_2_0.woff

138 ms

Homepage_Sacramento-scaled.jpg

Homepage_Sacramento-scaled.jpg

166 ms

events.js

events.js

155 ms

collect

collect

51 ms

bounce

bounce

56 ms

Accessibility Review

images.capitolcorridor.org accessibility score

96

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

Links do not have a discernible name

Best Practices

images.capitolcorridor.org 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

Displays images with incorrect aspect ratio

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

images.capitolcorridor.org 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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Images.capitolcorridor.org 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 Images.capitolcorridor.org 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

images.capitolcorridor.org

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