4.4 sec in total
134 ms
3.4 sec
876 ms
Click here to check amazing Stop Prop 16 content. Otherwise, check out these important facts you probably never knew about stopprop16.org
Prop 16 would repeal the California Civil Rights Initiative (Prop 209) that currently protects us all from discrimination. Vote no! Prop 16 won’t bring us equal opportunity or affirmative action, but ...
Visit stopprop16.orgWe analyzed Stopprop16.org page load time and found that the first response time was 134 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
stopprop16.org performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value6.0 s
13/100
25%
Value12.4 s
3/100
10%
Value6,190 ms
0/100
30%
Value0.038
100/100
15%
Value23.1 s
1/100
10%
134 ms
2551 ms
59 ms
114 ms
175 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 72% of them (47 requests) were addressed to the original Stopprop16.org, 28% (18 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Stopprop16.org.
Page size can be reduced by 172.2 kB (26%)
661.8 kB
489.5 kB
In fact, the total size of Stopprop16.org main page is 661.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 227.6 kB which makes up the majority of the site volume.
Potential reduce by 165.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 165.9 kB or 83% of the original size.
Potential reduce by 0 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. Stop Prop 16 images are well optimized though.
Potential reduce by 6.2 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 160 B
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. Stopprop16.org has all CSS files already compressed.
Number of requests can be reduced by 38 (86%)
44
6
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stop Prop 16. 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 18 to 1 for CSS and as a result speed up the page load time.
stopprop16.org
134 ms
stopprop16.org
2551 ms
twb-global.min.css
59 ms
ctf-styles.min.css
114 ms
font-awesome.min.css
175 ms
import-eventbrite-events-front.min.css
172 ms
ffwd_frontend.min.css
167 ms
ffwd_fonts.min.css
165 ms
ffwd_mCustomScrollbar.min.css
169 ms
wsm-style.min.css
167 ms
style-main-new.min.css
222 ms
elementor-icons.min.css
225 ms
frontend.min.css
229 ms
swiper.min.css
236 ms
post-130.css
225 ms
all.min.css
236 ms
v4-shims.min.css
276 ms
post-97.css
279 ms
ytprefs.min.css
281 ms
jquery.min.js
289 ms
jquery-migrate.min.js
303 ms
twb-circle.min.js
287 ms
twb-global.min.js
388 ms
ffwd_cache.min.js
388 ms
ffwd_frontend.min.js
388 ms
ffwd_jquery_mobile.min.js
388 ms
jquery.mCustomScrollbar.concat.min.js
389 ms
jquery-fullscreen.min.js
389 ms
ffwd_gallery_box.min.js
389 ms
v4-shims.min.js
394 ms
ytprefs.min.js
394 ms
animations.min.css
393 ms
lazysizes.min.js
397 ms
neve-script.min.js
398 ms
fitvids.min.js
437 ms
webpack.runtime.min.js
440 ms
frontend-modules.min.js
445 ms
waypoints.min.js
445 ms
core.min.js
404 ms
frontend.min.js
352 ms
lazyload.min.js
377 ms
wsm_new.js
298 ms
cropped-Stop-Prop-16-logo-gray-background.png
274 ms
A.jpg
364 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
125 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
147 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
187 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
220 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
260 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
259 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
260 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
260 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
218 ms
eicons.woff
305 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf
261 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0ow.ttf
262 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0ow.ttf
264 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXh0ow.ttf
265 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXh0ow.ttf
266 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXh0ow.ttf
267 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf
267 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0ow.ttf
268 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXh0ow.ttf
302 ms
Colored-Backgroud-150x150.png
143 ms
Screen-Shot-2021-01-28-at-4.10.24-PM-300x173.png
183 ms
stopprop16.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
stopprop16.org 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
Page has valid source maps
stopprop16.org 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
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 Stopprop16.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 Stopprop16.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.
stopprop16.org
Open Graph data is detected on the main page of Stop Prop 16. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: