6.7 sec in total
113 ms
5.9 sec
693 ms
Click here to check amazing Standbystatus content. Otherwise, check out these important facts you probably never knew about standbystatus.com
Generac offers programs for contractors who sell and install Generac products as well as a full line of contractor-grade products for work on the jobsite.
Visit standbystatus.comWe analyzed Standbystatus.com page load time and found that the first response time was 113 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
standbystatus.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value6.9 s
6/100
25%
Value6.9 s
33/100
10%
Value2,210 ms
6/100
30%
Value0.417
23/100
15%
Value16.4 s
5/100
10%
113 ms
122 ms
576 ms
42 ms
139 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Standbystatus.com, 45% (61 requests) were made to Generac.com and 9% (12 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Generac.com.
Page size can be reduced by 455.0 kB (26%)
1.7 MB
1.3 MB
In fact, the total size of Standbystatus.com main page is 1.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 989.3 kB which makes up the majority of the site volume.
Potential reduce by 66.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 66.1 kB or 61% of the original size.
Potential reduce by 46.1 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. Standbystatus images are well optimized though.
Potential reduce by 30.6 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 30.6 kB or 14% of the original size.
Potential reduce by 312.1 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. Standbystatus.com needs all CSS files to be minified and compressed as it can save up to 312.1 kB or 75% of the original size.
Number of requests can be reduced by 76 (62%)
122
46
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Standbystatus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
standbystatus.com
113 ms
mobilelink
122 ms
mobilelink
576 ms
ps-utid.js
42 ms
GetResource.ashx
139 ms
GetResource.ashx
157 ms
GetResource.ashx
182 ms
GetResource.ashx
225 ms
css2
67 ms
GetResource.ashx
189 ms
GetResource.ashx
185 ms
main.css
342 ms
globals.js
193 ms
vendor.js
416 ms
frontEnd-min.js
461 ms
GetResource.ashx
401 ms
GetResource.ashx
413 ms
WebResource.axd
434 ms
GetResource.ashx
473 ms
ScriptResource.axd
476 ms
ScriptResource.axd
474 ms
payload.js
480 ms
GetResource.ashx
480 ms
GetResource.ashx
481 ms
GetResource.ashx
482 ms
GetResource.ashx
481 ms
GetResource.ashx
480 ms
GetResource.ashx
493 ms
GetResource.ashx
493 ms
GetResource.ashx
497 ms
GetResource.ashx
497 ms
gtm.js
393 ms
loading.gif
249 ms
Google-Play-Store-Icon_150x50;;.aspx
247 ms
Apple-App-Store-Icon_150x50;;.aspx
249 ms
A3_1;;.aspx
348 ms
A3_2;;.aspx
247 ms
A3_3;;.aspx
248 ms
Mobile-Link-Value_Rt.png
1017 ms
Mobile-Link-Value.png
730 ms
Mobile-Link-TestimonyA_600x400_v2.jpg
556 ms
Mobile-Link-TestimonyB_600x400_v2_1.jpg
546 ms
Mobile-Link-TestimonyC_600x400_v2.jpg
546 ms
Mobile-Link-TestimonyD_600x400_v2.jpg
629 ms
Mobile-Link-TestimonyE_600x400_v2.jpg
629 ms
generac-logo.png
630 ms
GeneracIndustrialPower_black.png
629 ms
GeneracMobile_black.png
718 ms
logo_pramac.png
717 ms
Selmec_black.png
719 ms
DR_black.png
717 ms
Powermate_black.png
1005 ms
Motortech_black.png
1004 ms
Captiva_black.png
1004 ms
Enbala_black.png
1003 ms
Chilicon_black.png
1002 ms
TankUtility_BLACK.png
3260 ms
MeanGreenMowers_black.png
3257 ms
Ecobee_BLACK.png
3343 ms
bbb.png
1501 ms
KFOmCnqEu92Fr1Me5Q.ttf
509 ms
KFOkCnqEu92Fr1MmgWxP.ttf
523 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
524 ms
_qfouEosmts
826 ms
icon-search.svg
1279 ms
top-arrow.png
1288 ms
analytics.js
599 ms
conversion_async.js
1072 ms
bat.js
1283 ms
insight.min.js
628 ms
fbevents.js
996 ms
globals.js
1000 ms
up_loader.1.1.0.js
993 ms
ytc.js
989 ms
js
183 ms
s48596878887619
283 ms
www-player.css
780 ms
www-embed-player.js
863 ms
base.js
862 ms
fetch-polyfill.js
617 ms
fontawesome-webfont.woff
2347 ms
collect
417 ms
collect
790 ms
collect
653 ms
MobileLink-Homepage-Banner_1900x400.jpg
2131 ms
collect
380 ms
410 ms
10155827.json
231 ms
255741498253148
218 ms
velaro.inline.js
366 ms
iframe_api
153 ms
_qfouEosmts
148 ms
mobilelink
229 ms
5624430.js
124 ms
pixel
204 ms
www-widgetapi.js
122 ms
231016940664203
182 ms
ga-audiences
62 ms
ga-audiences
171 ms
www-embed-player.js
116 ms
base.js
522 ms
fetch-polyfill.js
112 ms
5624430
396 ms
generic
390 ms
velaro.inline.5e9277fb.js
131 ms
105 ms
824625711832229
196 ms
generic
390 ms
749 ms
clarity.js
328 ms
ttdsync
432 ms
ad_status.js
470 ms
VM1LbcxuQZ7urdjSm15-Kft2IdlldgxYJTjOL3p1Mjw.js
182 ms
embed.js
87 ms
velaro.inline.min.css
73 ms
id
127 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
26 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
27 ms
Create
193 ms
154 ms
118 ms
GetResource.ashx
155 ms
170 ms
nr-1216.min.js
125 ms
collect
108 ms
up
180 ms
inlinechat.min.css
45 ms
inlinechat.css
42 ms
279 ms
NRBR-ef93b6f128705e29fbf
160 ms
universal_pixel.1.1.0.js
7 ms
37 ms
GenerateIT
32 ms
rubicon
14 ms
generic
12 ms
appnexus
28 ms
c.gif
48 ms
standbystatus.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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
standbystatus.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
standbystatus.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
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Standbystatus.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 Standbystatus.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.
standbystatus.com
Open Graph data is detected on the main page of Standbystatus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: