getmaple.ca score is

Top Technologies
CloudFlare
CDN
Google Font API
Font Scripts
WordPress
CMS
Nginx
Web Servers
Font Awesome
Font Scripts
Apache
Web Servers
Twitter Bootstrap
Web Frameworks
Google Tag Manager
Tag Managers

26 getmaple.ca Last Updated: 6 months

Success 62% of passed verification steps
Warning 23% of total warning
Errors 15% of total errors, require fast action

Desktop Speed Score

Mobile Speed Score

Performance Desktop Score 81%
Best Practices Desktop Score 80%
SEO Desktop Score 83%
Progressive Web App Desktop Score 45%
Performance Mobile Score 28%
Best Practices Mobile Score 80%
SEO Mobile Score 81%
Progressive Web App Mobile Score 50%
Page Authority Authority 37%
Domain Authority Domain Authority 42%
Moz Rank 3.7/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 67 Characters
MAPLE: ONLINE DOCTORS, VIRTUAL HEALTH & PRESCRIPTIONS IN CANADA
Meta Description 149 Characters
With Maple you can now see a doctor in minutes, anytime 24/7. Online consultations with Canadian-licensed doctors for medical advice & treatment.
Effective URL 19 Characters
https://getmaple.ca
Excerpt Page content
Maple: Online Doctors, Virtual Health & Prescriptions in Canada UTILISEZ VOTREnavigateur web Skip to main content. Skip to chat with us. Maple Company Logo Register Features How it works Online prescriptions Sick notes Lab work Our doctors Pricing Specialties Dermatology Mole Mapping Psychiatry Psychotherapy Endocrinology Naturopathy Allergy & Immunology Caregiver Coaching Functional Medicine See all Work with us Business Hospitals Register Sign in Français Download on the App Store ...
Keywords Cloud Density
maple15 review11 doctors10 doctor9 click7 facebook7 open6 store6 learn5 time5
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
maple 15
review 11
doctors 10
doctor 9
click 7
facebook 7
open 6
store 6
learn 5
time 5
Google Preview Your look like this in google search result
MAPLE: ONLINE DOCTORS, VIRTUAL HEALTH & PRESCRIPTIONS IN
https://getmaple.ca
With Maple you can now see a doctor in minutes, anytime 24/7. Online consultations with Canadian-licensed doctors for medical advice & treatment.
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~260.25 KB
Code Size: ~231.56 KB
Text Size: ~28.69 KB Ratio: 11.03%

getmaple.ca Estimation Traffic and Earnings

15,622
Unique Visits
Daily
28,900
Pages Views
Daily
$19
Income
Daily
437,416
Unique Visits
Monthly
823,650
Pages Views
Monthly
$475
Income
Monthly
5,061,528
Unique Visits
Yearly
9,710,400
Pages Views
Yearly
$5,016
Income
Yearly

Desktop Speed Score

Desktop Screenshot
Links do not have descriptive text 4 links found
Descriptive link text helps search engines understand your content
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
Efficiently encode images Potential savings of 225 KiB
Optimized images load faster and consume less cellular data
Keep request counts low and transfer sizes small 139 requests • 2,921 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Estimated Input Latency 20 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
Avoid enormous network payloads Total size was 2,921 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Avoid an excessive DOM size 2,123 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)
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index 1.9 s
Speed Index shows how quickly the contents of a page are visibly populated
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
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 multiple page redirects Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded
First CPU Idle 2.2 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/).
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible
Minimizes main-thread work 1.9 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.245
Cumulative Layout Shift measures the movement of visible elements within the viewport
Remove unused CSS Potential savings of 22 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
Total Blocking Time 100 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid non-composited animations 3 animated elements found
Animations which are not composited can be janky and increase CLS
Eliminate render-blocking resources Potential savings of 120 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Serve images in next-gen formats Potential savings of 845 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Serve static assets with an efficient cache policy 99 resources found
A long cache lifetime can speed up repeat visits to your page
Initial server response time was short Root document took 480 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests 30 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
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
Max Potential First Input Delay 110 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Time to Interactive 2.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint 2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Remove unused JavaScript Potential savings of 239 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Properly size images Potential savings of 27 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Enable text compression Potential savings of 10 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Avoid serving legacy JavaScript to modern browsers Potential savings of 24 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
JavaScript execution time 0.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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

Mobile Speed Score

Mobile Screenshot
Tap targets are not sized appropriately 39% 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
Efficiently encode images Potential savings of 96 KiB
Optimized images load faster and consume less cellular data
Serve static assets with an efficient cache policy 84 resources found
A long cache lifetime can speed up repeat visits to your page
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
First Contentful Paint (3G) 5076 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Avoid large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page.
Avoid an excessive DOM size 2,123 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 490 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS
Time to Interactive 13.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Estimated Input Latency 200 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
Enable text compression Potential savings of 10 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Minimize main-thread work 9.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Document uses legible font sizes 98.47% 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
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
Avoid chaining critical requests 30 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
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 2,702 KiB
Large network payloads cost users real money and are highly correlated with long load times
Properly size images Potential savings of 31 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Reduce the impact of third-party code Third-party code blocked the main thread for 490 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 Meaningful Paint 3.9 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused JavaScript Potential savings of 239 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Keep request counts low and transfer sizes small 124 requests • 2,702 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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 Index 6.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 800 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Serve images in next-gen formats Potential savings of 687 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
First CPU Idle 11.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/).
Total Blocking Time 2,180 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid multiple page redirects Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
Remove unused CSS Potential savings of 23 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 470 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
Links do not have descriptive text 4 links found
Descriptive link text helps search engines understand your content
First Contentful Paint 2.7 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint 5.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce JavaScript execution time 5.0 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.191
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 24 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

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
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
Congratulations! Your Domain Authority is good
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

getmaple.ca Alexa Rank

91,728

Global Rank

3,393

Canada
Traffic getmaple.ca Traffic
Search getmaple.ca Search

Domain Available

Domain (TDL) and Typo Status
getmaple.co Available Buy Now!
getmaple.us Available Buy Now!
getmaple.com Available Buy Now!
getmaple.org Available Buy Now!
getmaple.net Available Buy Now!
gtmaple.ca Available Buy Now!
tetmaple.ca Available Buy Now!
betmaple.ca Available Buy Now!

Information Server getmaple.ca

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 301 
server: nginx
date: Tue, 13 Apr 2021 19:39:45 GMT
content-type: text/html; charset=UTF-8
content-length: 0
location: https://www.getmaple.ca/
x-pingback:
x-redirect-by: WordPress
cache-control: max-age=2592000
expires: Thu, 13 May 2021 18:47:09 GMT
age: 3155
x-cache: HIT
access-control-allow-origin: *
DNS Records DNS Resource Records associated with a hostname
getmaple.ca View DNS Records

Social Data