6.2 sec in total
261 ms
5.3 sec
644 ms
Click here to check amazing Proterra content for United States. Otherwise, check out these important facts you probably never knew about proterra.com
Building innovative battery technologies to power a better, more sustainable world.
Visit proterra.comWe analyzed Proterra.com page load time and found that the first response time was 261 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 75% of websites can load faster.
proterra.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value10.0 s
0/100
25%
Value10.9 s
6/100
10%
Value2,600 ms
4/100
30%
Value0.001
100/100
15%
Value11.2 s
20/100
10%
261 ms
452 ms
42 ms
69 ms
53 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 84% of them (90 requests) were addressed to the original Proterra.com, 4% (4 requests) were made to Unpkg.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Cloud.typography.com.
Page size can be reduced by 175.9 kB (12%)
1.5 MB
1.3 MB
In fact, the total size of Proterra.com main page is 1.5 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 151.9 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 151.9 kB or 85% of the original size.
Potential reduce by 57 B
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. Proterra images are well optimized though.
Potential reduce by 50 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 23.9 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. Proterra.com needs all CSS files to be minified and compressed as it can save up to 23.9 kB or 68% of the original size.
Number of requests can be reduced by 57 (58%)
98
41
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Proterra. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
proterra.com
261 ms
www.proterra.com
452 ms
tooltips_main.css
42 ms
tooltips_styles.css
69 ms
js_composer.min.css
53 ms
style-frontend.php
486 ms
close-button-icon.css
69 ms
YouTubePopUp.css
71 ms
fonts.css
2205 ms
style.css
80 ms
wpex-mobile-menu-breakpoint-min.css
77 ms
style.css
96 ms
wpex-wpbakery.css
101 ms
ticons.min.css
98 ms
vcex-shortcodes.css
101 ms
upw-theme-standard.min.css
103 ms
main.css
105 ms
the-grid.min.css
120 ms
jquery.min.js
122 ms
jquery-migrate.min.js
173 ms
frontend-script.js
127 ms
YouTubePopUp.jquery.js
125 ms
YouTubePopUp.js
148 ms
wonderpluginvideoembed.js
145 ms
css
41 ms
flickity.min.css
83 ms
animate.min.css
82 ms
frontend-style.css
101 ms
flickity-fade.css
110 ms
animate.min.css
114 ms
style.css
119 ms
script.js
133 ms
cookiebanner.js
123 ms
cookiebanner-init.js
136 ms
webfont.js
208 ms
jquery.easing.min.js
143 ms
total.min.js
150 ms
isotope.js
151 ms
asp.js
158 ms
common.js
174 ms
effect.min.js
192 ms
the-grid.min.js
176 ms
js_composer_front.min.js
183 ms
flickity.pkgd.min.js
193 ms
flickity-fade.js
197 ms
vc-waypoints.min.js
204 ms
jquery.uniform.min.js
199 ms
custom.js
195 ms
idle-timer.min.js
193 ms
wpex-vc_waypoints.min.js
198 ms
wpex-mobile-menu-breakpoint-max.css
33 ms
B9E97526EB884AD7D.css
203 ms
gtm.js
469 ms
home-feat-2.jpg
504 ms
410 ms
Proterra-Logo.png
405 ms
favicon-proterra.png
405 ms
ZX5-40-Foot-Bus-3.png
407 ms
BATTERY-compressed.jpeg
406 ms
ZX5-40-Foot-Bus-compressed.jpg
405 ms
CHARGING-compressed.jpeg
405 ms
CONNECTED-VEHICLES-compressed.jpg
556 ms
DRIVETRAIN-compressed.jpeg
410 ms
logo-via-300x200.png
410 ms
logo-wego-300x200.png
412 ms
logo-starmetro-300x200.png
409 ms
logo-king-county-metro-300x200.png
408 ms
logo-dta-300x200.png
413 ms
logo-dart-dallas-300x200.png
411 ms
logo-septa-300x200.png
553 ms
logo-metrolink-300x200.png
552 ms
logo-vta-300x200.png
836 ms
logo-park-city-300x200.png
836 ms
logo-pierce-transit-300x200.png
835 ms
logo-dart-delaware-300x200.png
554 ms
logo-everett-transit-300x200.png
834 ms
logo-sportran-300x200.png
834 ms
logo-pat-300x200.png
835 ms
logo-tarc-300x200.png
838 ms
logo-foothill-transit-300x200.png
837 ms
logo-wrta-300x200.png
838 ms
logo-rtd-300x200.png
1078 ms
logo-catbus-transit-300x200.png
837 ms
logo-rtc-300x200.png
839 ms
logo-kitsap-300x200.png
1077 ms
logo-jll-300x200.png
1076 ms
logo-visalia-300x200.png
1077 ms
white-logo-proterra-retina.png
1077 ms
home-1-2.jpg
407 ms
ticons.woff
967 ms
icomoon.ttf
969 ms
the_grid.ttf
968 ms
674 ms
invisible.js
534 ms
analytics.js
511 ms
js
509 ms
18b2fca020614e687ff85bb3a6895ecf74fe24a7-compiled-public-forms.css
531 ms
css2
194 ms
react.production.min.js
540 ms
react-dom.production.min.js
541 ms
e171f1f0a6e9238dce4f834c5e21b92f707a83de-compiled-public-forms.js
537 ms
collect
240 ms
collect
299 ms
react.production.min.js
224 ms
react-dom.production.min.js
263 ms
7527227038eb5c82
128 ms
nr-spa-1216.min.js
86 ms
proterra.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
proterra.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
proterra.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Proterra.com 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 Proterra.com 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.
proterra.com
Open Graph data is detected on the main page of Proterra. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: