1.3 sec in total
195 ms
1 sec
66 ms
Click here to check amazing Braintumourwalk content for Canada. Otherwise, check out these important facts you probably never knew about braintumourwalk.ca
Visit braintumourwalk.caWe analyzed Braintumourwalk.ca page load time and found that the first response time was 195 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
braintumourwalk.ca performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value26.2 s
0/100
25%
Value19.5 s
0/100
10%
Value9,240 ms
0/100
30%
Value0.524
15/100
15%
Value38.3 s
0/100
10%
195 ms
36 ms
53 ms
64 ms
34 ms
Our browser made a total of 19 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Braintumourwalk.ca, 37% (7 requests) were made to Btfc.akaraisin.com and 5% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (195 ms) relates to the external source Btfc.akaraisin.com.
Page size can be reduced by 276.7 kB (25%)
1.1 MB
840.8 kB
In fact, the total size of Braintumourwalk.ca main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 848.7 kB which makes up the majority of the site volume.
Potential reduce by 175.8 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 175.8 kB or 89% of the original size.
Potential reduce by 90.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 90.2 kB or 11% of the original size.
Potential reduce by 10.7 kB
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. Braintumourwalk.ca needs all CSS files to be minified and compressed as it can save up to 10.7 kB or 15% of the original size.
Number of requests can be reduced by 16 (89%)
18
2
The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Braintumourwalk. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
{{url}}
{{time}} ms
braintumourwalk.ca 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 progressbar elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
braintumourwalk.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
braintumourwalk.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Braintumourwalk.ca can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Braintumourwalk.ca 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.
{{og_description}}
braintumourwalk.ca
Open Graph description is not detected on the main page of Braintumourwalk. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: