Your Website Score is
16 tomorrowwevote.org Last Updated: 3 years
Success
54% of passed verification steps
Warning
23% of total warning
Errors
23% of total errors, require fast action
Share
Desktop
Mobile
Page Authority
Authority 28%
Domain Authority
Domain Authority 15%
Moz Rank
2.8/10
Bounce Rate
Rate 0%
charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
60 Characters
TOMORROW WE VOTE | YOUTH ENGAGEMENT & VOTER REGISTRATION
Meta Description
133 Characters
Tomorrow We Vote is a Black and Brown-led non-partisan, nonprofit Arizona-based organization empowering the youth through their vote.
Effective URL
25 Characters
http://tomorrowwevote.org
Excerpt
Page content
Tomorrow We Vote | Youth Engagement & Voter Registration
Skip to content
Tomorrow We Vote
Home
About Us
T...
Google Preview
Your look like this in google search result
TOMORROW WE VOTE | YOUTH ENGAGEMENT & VOTER REGISTRATION
http://tomorrowwevote.org
Tomorrow We Vote is a Black and Brown-led non-partisan, nonprofit Arizona-based organization empowering the youth through their vote.
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~182.84 KB
Code Size: ~103.42 KB
Text Size: ~79.42 KB Ratio: 43.44%
Social Data
Estimation Traffic and Earnings
8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly
Desktop
Mobile
Links do not have descriptive text
4 links found
Descriptive link text helps search engines understand your content
Reduce initial server response time
Root document took 1,040 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Defer offscreen images
Potential savings of 507 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Tap targets are not sized appropriately
77% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Avoid chaining critical requests
82 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Reduce unused JavaScript
Potential savings of 657 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
User Timing marks and measures
11 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Largest Contentful Paint
16.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,540 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
First Contentful Paint
5.2 s
First Contentful Paint marks the time at which the first text or image is painted
Document uses legible font sizes
100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Keep request counts low and transfer sizes small
142 requests • 3,633 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded
Total Blocking Time
1,200 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Max Potential First Input Delay
360 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint (3G)
11204 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Minimize main-thread work
9.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Reduce unused CSS
Potential savings of 387 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid large layout shifts
3 elements found
These DOM elements contribute most to the CLS of the page.
Uses efficient cache policy on static assets
6 resources found
A long cache lifetime can speed up repeat visits to your page
Reduce JavaScript execution time
3.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Efficiently encode images
Potential savings of 57 KiB
Optimized images load faster and consume less cellular data
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser
Avoid non-composited animations
71 animated elements found
Animations which are not composited can be janky and increase CLS
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Avoid enormous network payloads
Total size was 3,633 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index
11.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid serving legacy JavaScript to modern browsers
Potential savings of 18 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
First Meaningful Paint
5.2 s
First Meaningful Paint measures when the primary content of a page is visible
Eliminate render-blocking resources
Potential savings of 3,310 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid an excessive DOM size
992 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Time to Interactive
23.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Cumulative Layout Shift
0.02
Cumulative Layout Shift measures the movement of visible elements within the viewport
Properly size images
Potential savings of 94 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Serve images in next-gen formats
Potential savings of 692 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Some third-party resources can be lazy loaded with a facade
1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required
Speed And Optimization Tips
Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (HTTPS).
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Warning! You have broken links
View links
| First 20 Links | Relationship | HTTP Status |
| Tomorrow We Vote | Internal Link | 200 |
| Home | Internal Link | 200 |
| About Us | Internal Link | 200 |
| Tomorrow We Vote Action | Internal Link | 0 |
| Board of Directors | Internal Link | 200 |
| News | Internal Link | 200 |
| Voting Centers | Internal Link | 200 |
| Alabama Center | Internal Link | 200 |
| Alaska Center | Internal Link | 200 |
| Arizona Center | Internal Link | 200 |
| Arkansas Center | Internal Link | 200 |
| California Center | Internal Link | 200 |
| Colorado Center | Internal Link | 200 |
| Connecticut Center | Internal Link | 200 |
| Delaware Center | Internal Link | 200 |
| Florida Center | Internal Link | 200 |
| Georgia Center | Internal Link | 200 |
| Hawaii Center | Internal Link | 200 |
| Idaho Center | Internal Link | 200 |
| Illinois Center | Internal Link | 200 |
Alexa Rank
99,999,999
Global Rank99,999,999
-
Traffic
Search
Domain Available
| Domain (TDL) and Typo | Status |
|---|---|
| tomorrowwevote.co | Available |
| tomorrowwevote.us | Available |
| tomorrowwevote.com | Already Registered |
| tomorrowwevote.org | Already Registered |
| tomorrowwevote.net | Available |
| tmorrowwevote.org | Available |
| vomorrowwevote.org | Available |
| gomorrowwevote.org | Available |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 500 Internal Server Error
Date: Wed, 14 Sep 2022 21:48:04 GMT
Content-Type: text/html; charset=iso-8859-1
Connection: keep-alive
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=PYJnoB7uG2vKnP%2FqOc%2FPtPGBON1GxM1mEhzcskV%2FWu4dMra02eIx4FoAPgPkyci5S3M2uVnh1J22uLWtYP4kMmY6GixIsGwMy0u53XLHhn8j9p2ryWPmPo384Ty89LS5YIBfK6o%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 74ac5320895654b5-YYZ
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400