Your Website Score is
SEO Rank : 2 Website URL: myschedule.metro.ca Last Updated: 5 months
Success
39% of passed verification steps
Warning
15% of total warning
Errors
46% of total errors, require fast action
Share
Estimation Traffic and Earnings
2,487
Unique Visits
Daily
4,600
Pages Views
Daily
$10
Income
Daily
69,636
Unique Visits
Monthly
131,100
Pages Views
Monthly
$250
Income
Monthly
805,788
Unique Visits
Yearly
1,545,600
Pages Views
Yearly
$2,640
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 0%
Domain Authority
Domain Authority 0%
Moz Rank
0.0/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
0 Characters
NO DATA
Meta Description
52 Characters
Displaying Metro Employees Work Schedules in Ontario
Effective URL
27 Characters
https://myschedule.metro.ca
Meta Keywords
5 Detected
Google Preview
Your look like this in google search result
myschedule.metro.ca
https://myschedule.metro.ca
Displaying Metro Employees Work Schedules in Ontario
Robots.txt
File No Found
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~6.28 KB
Code Size: ~5.07 KB
Text Size: ~1.21 KB Ratio: 19.26%
Social Data
Desktop
Remove unused JavaScript
Potential savings of 96 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Serve static assets with an efficient cache policy
46 resources found
A long cache lifetime can speed up repeat visits to your page
Minimize third-party usage
Third-party code blocked the main thread for 0 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
Initial server response time was short
Root document took 350 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources
Potential savings of 90 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint
2.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Avoid large layout shifts
4 elements found
These DOM elements contribute most to the CLS of the page.
Speed Index
1.6 s
Speed Index shows how quickly the contents of a page are visibly populated
JavaScript execution time
0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First CPU Idle
1.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Includes front-end JavaScript libraries with known security vulnerabilities
16 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Keep request counts low and transfer sizes small
56 requests • 407 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids an excessive DOM size
129 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)
Max Potential First Input Delay
160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Estimated Input Latency
10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Time to Interactive
2.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Minimizes main-thread work
0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Remove unused CSS
Potential savings of 19 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Minify JavaScript
Potential savings of 18 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Total Blocking Time
150 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid chaining critical requests
39 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
Cumulative Layout Shift
0.007
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoids enormous network payloads
Total size was 407 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
First Contentful Paint
1.5 s
First Contentful Paint marks the time at which the first text or image is painted
First Meaningful Paint
1.5 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid long main-thread tasks
3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Mobile
Time to Interactive
7.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint
7.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First CPU Idle
6.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Cumulative Layout Shift
0.008
Cumulative Layout Shift measures the movement of visible elements within the viewport
Tap targets are sized appropriately
100% 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
Serve static assets with an efficient cache policy
46 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint
5.3 s
First Contentful Paint marks the time at which the first text or image is painted
Remove unused JavaScript
Potential savings of 96 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Total Blocking Time
1,390 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
Includes front-end JavaScript libraries with known security vulnerabilities
16 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First Contentful Paint (3G)
11843 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Avoid chaining critical requests
39 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
Avoids enormous network payloads
Total size was 407 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minify JavaScript
Potential savings of 18 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoids an excessive DOM size
129 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)
Speed Index
6.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Minimize main-thread work
4.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks
12 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Defer offscreen images
Potential savings of 9 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
First Meaningful Paint
5.7 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small
57 requests • 407 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Document uses legible font sizes
89.78% 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
Max Potential First Input Delay
1,660 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Remove unused CSS
Potential savings of 19 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Initial server response time was short
Root document took 380 ms
Keep the server response time for the main document short because all other requests depend on it
Estimated Input Latency
480 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Eliminate render-blocking resources
Potential savings of 480 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Preload key requests
Potential savings of 570 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
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
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
Reduce JavaScript execution time
2.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minimize third-party usage
Third-party code blocked the main thread for 0 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
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
Warning! Your title is not optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
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
Congratulations! You not have broken links
View links
| First 0 Links | Relationship | HTTP Status |
Alexa Rank
823
Local Rank: CA / Users: 85.8% / PageViews: 96.6%41,752
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| myschedule.metro.co | Available Buy Now! |
| myschedule.metro.us | Already Registered |
| myschedule.metro.com | Available Buy Now! |
| myschedule.metro.org | Already Registered |
| myschedule.metro.net | Available Buy Now! |
| mschedule.metro.ca | Already Registered |
| jyschedule.metro.ca | Already Registered |
| iyschedule.metro.ca | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Thu, 13 Aug 2020 23:39:29 GMT
content-type: text/html
set-cookie: __cfduid=d3a9270f5b54a0129459314fb3dc8b8ca1597361969; expires=Sat, 12-Sep-20 23:39:29 GMT; path=/; domain=.metro.ca; HttpOnly; SameSite=Lax
x-powered-by: ASP.NET
x-robots-tag: all
cf-cache-status: DYNAMIC
cf-request-id: 048bca6f7b0000e7d9b1a19200000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
set-cookie: __cf_bm=20d9970a03ce091dedd9c06a7c22978b19d6ea56-1597361969-1800-AXDMN0qdIgMJLiy7sRcdR9k2u/EqgU95F5wX2nmNrhatjgk5+pdhSFr453fbohZM6dPU9gGPprH+lfsdywdySLE=; path=/; expires=Fri, 14-Aug-20 00:09:29 GMT; domain=.metro.ca; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 5c2646925b57e7d9-LAX
content-encoding: gzip
Click to Add/Show Comments