6.5 sec in total
229 ms
5.9 sec
434 ms
Welcome to standaz.com homepage info - get ready to check Stand Az best content for United States right away, or after learning these important things about standaz.com
Students Taking a New Direction. Students and teens stand up against tobacco in Arizona. Learn the best ways on how to stop smoking.
Visit standaz.comWe analyzed Standaz.com page load time and found that the first response time was 229 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
standaz.com performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value5.6 s
17/100
25%
Value9.9 s
10/100
10%
Value1,380 ms
16/100
30%
Value0.357
30/100
15%
Value22.4 s
1/100
10%
229 ms
1993 ms
538 ms
400 ms
653 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 66% of them (46 requests) were addressed to the original Standaz.com, 6% (4 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Standaz.com.
Page size can be reduced by 126.8 kB (8%)
1.6 MB
1.5 MB
In fact, the total size of Standaz.com main page is 1.6 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. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 41.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 41.2 kB or 75% of the original size.
Potential reduce by 70.7 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. Stand Az images are well optimized though.
Potential reduce by 9.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. This website has mostly compressed JavaScripts.
Potential reduce by 5.4 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. Standaz.com has all CSS files already compressed.
Number of requests can be reduced by 36 (58%)
62
26
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stand Az. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
standaz.com
229 ms
www.standaz.com
1993 ms
wp-emoji-release.min.js
538 ms
normalize.css
400 ms
glyphicons.css
653 ms
css
69 ms
style.css
511 ms
600.css
411 ms
960.css
597 ms
style.min.css
835 ms
jquery.min.js
56 ms
formreset.min.css
1010 ms
formsmain.min.css
1186 ms
readyclass.min.css
933 ms
browsers.min.css
998 ms
comment-reply.min.js
1062 ms
plugins.js
1296 ms
script.js
1387 ms
regenerator-runtime.min.js
1434 ms
wp-polyfill.min.js
1599 ms
dom-ready.min.js
1440 ms
hooks.min.js
1542 ms
i18n.min.js
1677 ms
a11y.min.js
1759 ms
jquery.json.min.js
1801 ms
gravityforms.min.js
2082 ms
all.js
36 ms
widgets.js
300 ms
iframe_api
134 ms
sidebarv2.js
136 ms
0.jpg
134 ms
0.jpg
171 ms
0.jpg
285 ms
bg-pattern-asphalt.jpg
1123 ms
thecignal-footer-bg.png
1293 ms
dont-get-manipulated-featured-img1.jpg
1183 ms
Infographic-21.png
1301 ms
gtm.js
172 ms
logo-stand.png
1288 ms
logo-counterstrike.png
1517 ms
logo-itmatters.png
1675 ms
glyphicons-white-search.png
1577 ms
glyphicons-facebook.png
1623 ms
glyphicons-twitter.png
1657 ms
glyphicons-instagram.png
1715 ms
glyphicons-facebook-white.png
1917 ms
glyphicons-white.png
2422 ms
glyphicons-twitter-white.png
2072 ms
glyphicons-instagram-white.png
2012 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e4.woff
162 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYw.woff
247 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYw.woff
262 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYw.woff
263 ms
glyphicons-regular.woff
2317 ms
www-widgetapi.js
64 ms
analytics_debug.js
132 ms
js
61 ms
collect
68 ms
collect
9 ms
glyphicons-facebook@2x.png
1745 ms
glyphicons-twitter@2x.png
1791 ms
glyphicons-instagram@2x.png
1905 ms
glyphicons-facebook@2x-white.png
2042 ms
glyphicons-twitter@2x-white.png
2194 ms
glyphicons-instagram@2x-white.png
2221 ms
analytics.js
39 ms
collect
108 ms
all.js
27 ms
widget_iframe.7dae38096d06923d683a2a807172322a.html
179 ms
settings
161 ms
standaz.com accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
standaz.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
Browser errors were logged to the console
Page has valid source maps
standaz.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Standaz.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 Standaz.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.
standaz.com
Open Graph data is detected on the main page of Stand Az. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: