Your Website Score is
SEO Rank : 44 Website URL: mysite.canadapost.ca Last Updated: 3 months
Success
54% of passed verification steps
Warning
23% of total warning
Errors
23% of total errors, require fast action
Share
Estimation Traffic and Earnings
18,721
Unique Visits
Daily
34,633
Pages Views
Daily
$66
Income
Daily
524,188
Unique Visits
Monthly
987,041
Pages Views
Monthly
$1,650
Income
Monthly
6,065,604
Unique Visits
Yearly
11,636,688
Pages Views
Yearly
$17,424
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 47%
Domain Authority
Domain Authority 75%
Moz Rank
4.7/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
20 Characters
SAP NETWEAVER PORTAL
Meta Description
0 Characters
NO DATA
Effective URL
39 Characters
https://mysite.canadapost.ca/irj/portal
Excerpt
Page content
SAP NetWeaver Portal L'iView n'a pas pu être ouverte. Elle n'est pas compatible avec votre navigateur, votre système d'exploitati...
Google Preview
Your look like this in google search result
SAP NETWEAVER PORTAL
https://mysite.canadapost.ca/irj/portal
SAP NetWeaver Portal L'iView n'a pas pu être ouverte. Elle n'est pas compatible avec votre navigateur, votre système d'exploitati...
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~1.46 KB
Code Size: ~745 B
Text Size: ~754 B Ratio: 50.30%
Social Data
Delicious
Total: 0
Facebook
Total: 140
Google
Total: 0
Linkedin
Total: 0
Pinterest
Total: 0
Stumbleupon
Total: 0
Tumblr
Total: 0
Vk
Total: 0
Desktop
Remove unused CSS
Potential savings of 54 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
Time to Interactive
0.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Cumulative Layout Shift
0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Max Potential First Input Delay
30 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Uses efficient cache policy on static assets
10 resources found
A long cache lifetime can speed up repeat visits to your page
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
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids an excessive DOM size
64 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)
Largest Contentful Paint
0.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Initial server response time was short
Root document took 300 ms
Keep the server response time for the main document short because all other requests depend on it
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
Avoid chaining critical requests
13 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
First Meaningful Paint
0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small
16 requests • 184 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids enormous network payloads
Total size was 184 KiB
Large network payloads cost users real money and are highly correlated with long load times
First CPU Idle
0.9 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/).
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
Avoid large layout shifts
4 elements found
These DOM elements contribute most to the CLS of the page.
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Minimizes main-thread work
0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
JavaScript execution time
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index
1.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Mobile
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
Remove unused CSS
Potential savings of 54 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
JavaScript execution time
0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift
0.055
Cumulative Layout Shift measures the movement of visible elements within the viewport
Initial server response time was short
Root document took 290 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint
3.1 s
First Contentful Paint marks the time at which the first text or image is painted
First CPU Idle
3.1 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/).
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
First Meaningful Paint
3.1 s
First Meaningful Paint measures when the primary content of a page is visible
Speed Index
3.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid chaining critical requests
12 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 173 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
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
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
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
First Contentful Paint (3G)
6103 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
3.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Total Blocking Time
30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Uses efficient cache policy on static assets
10 resources found
A long cache lifetime can speed up repeat visits to your page
Keep request counts low and transfer sizes small
15 requests • 173 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Max Potential First Input Delay
70 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids an excessive DOM size
64 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
3.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Eliminate render-blocking resources
Potential savings of 1,770 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
Minimizes main-thread work
0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Warning! Your description is not 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
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
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links
View links
| First 0 Links | Relationship | HTTP Status |
Alexa Rank
58
Local Rank: CA / Users: 85.0% / PageViews: 89.4%2,650
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| mysite.canadapost.co | Already Registered |
| mysite.canadapost.us | Already Registered |
| mysite.canadapost.com | Already Registered |
| mysite.canadapost.org | Already Registered |
| mysite.canadapost.net | Already Registered |
| msite.canadapost.ca | Already Registered |
| jysite.canadapost.ca | Already Registered |
| iysite.canadapost.ca | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Thu, 05 Nov 2020 00:00:24 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Keep-Alive: timeout=20
set-cookie: com.sap.engine.security.authentication.original_application_url=HEAD#izL9rBU8wwMSq4tviDvhJW8KS797q8RnloBNlTJbN1OOjCnlhaUohiHbv4PxqtVCLwG6lX7%2FC1JJQHQEdWOnqY8dyl5LyW1PjF3laT64dgA%3D;Path=/irj;HttpOnly
pragma: no-cache
cache-control: no-store, no-cache, must-revalidate
expires: 0
content-encoding: gzip
set-cookie: PortalAlias=portal; Path=/
set-cookie: saplb_*=(J2EE228550920)228550951; Version=1; Path=/
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000
Content-Security-Policy: connect-src 'self'
Click to Add/Show Comments