1.4 sec in total
135 ms
999 ms
248 ms
Click here to check amazing Grapevine content for Canada. Otherwise, check out these important facts you probably never knew about grapevine.ca
Visit grapevine.caWe analyzed Grapevine.ca page load time and found that the first response time was 135 ms and then it took 1.2 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.
grapevine.ca performance score
name
value
score
weighting
Value11.5 s
0/100
10%
Value15.8 s
0/100
25%
Value34.1 s
0/100
10%
Value1,710 ms
11/100
30%
Value0.014
100/100
15%
Value21.8 s
1/100
10%
135 ms
53 ms
55 ms
55 ms
59 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 78% of them (47 requests) were addressed to the original Grapevine.ca, 5% (3 requests) were made to Google-analytics.com and 5% (3 requests) were made to Static.olark.com. The less responsive or slowest element that took the longest time to load (423 ms) belongs to the original domain Grapevine.ca.
Page size can be reduced by 569.0 kB (47%)
1.2 MB
645.7 kB
In fact, the total size of Grapevine.ca main page is 1.2 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. 40% of websites need less resources to load. Images take 493.9 kB which makes up the majority of the site volume.
Potential reduce by 39.3 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 39.3 kB or 78% of the original size.
Potential reduce by 27.2 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Grapevine images are well optimized though.
Potential reduce by 255.4 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 255.4 kB or 68% of the original size.
Potential reduce by 247.1 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. Grapevine.ca needs all CSS files to be minified and compressed as it can save up to 247.1 kB or 84% of the original size.
Number of requests can be reduced by 29 (50%)
58
29
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grapevine. 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 11 to 1 for CSS and as a result speed up the page load time.
grapevine.ca
135 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
53 ms
css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css
55 ms
css_KH8uyEUxYF1ifID5UppUXrj46RAoAQrSirE2K_Yi7xk.css
55 ms
css_Q3BMm9EtgU0NUNkR9SWSH1bfshluRCpfuJHuJoW5MUU.css
59 ms
select2.css
79 ms
css_w3KSSLLNl1TkwYuWUm7rU0cBD-HWDG5x7Gxbpwf1-bo.css
80 ms
jquery-ui.css
151 ms
css_caiVAigDqIUiIOjZ532VtfG6ZA4dP4ZQO9k-5wKoGhw.css
102 ms
css_sxnFZkdASvGgmARSDQVOQyneRQrpi0BR8TK2fgjRBVE.css
109 ms
js_JLxuxbhhrFRy-sBnijHkR0TGGHgiukMPv94zvDWgQ3g.js
159 ms
js_obFUyTbqtcoGQtszVI46l1_oD927PzlDtlr_ilpYBqE.js
129 ms
js_9HH8xm7ebvDq8-JNa8m6Z-tMQGKbZjH6Jf085fhWboI.js
131 ms
js_Yu__bskBIyexYU6L7-ghgCOS82DPAf-WUqHcZp8H_Dc.js
158 ms
js_WVLaPyCUDa5fUv4VxBkvaiHEil8RN0mZzOyqtBgF03Q.js
182 ms
js_TICNXf_1XvUIyOXnZE4lRNfM9bSsbHHk-2vSc2aSHuI.js
231 ms
js_qZUUwooKgf5zEiDU4l_SA4BKPYEQJoxdtHZ9-I1tepQ.js
190 ms
js_43n5FBy8pZxQHxPXkf-sQF7ZiacVZke14b0VlvSA554.js
201 ms
css
24 ms
conversion.js
14 ms
css
17 ms
analytics.js
20 ms
collect
67 ms
collect
137 ms
gvvipbuyer.png
110 ms
gvmortgagesbg.png
109 ms
menu-leaf.png
107 ms
social_icons.png
107 ms
logo.png
106 ms
quick-search-arrow.png
105 ms
cluster-sm.png
156 ms
banner-img.jpg
354 ms
red_button.png
158 ms
blue_button.png
158 ms
featured-tag.png
176 ms
4484_GV_homepage_right_march1eng.jpg
224 ms
ABP_WebGraphicsUpdate_Slider.png
255 ms
slider-previous.jpg
206 ms
slider-next.jpg
207 ms
85d58302-856e-4d79-8c53-828cc0695a0d.jpg
225 ms
Winter%202016.jpg
263 ms
1%20Property%20Front.jpg
263 ms
IMG_2168_0.JPG
273 ms
P1020591_0.JPG
275 ms
Outside_48.jpg
305 ms
IMG_0345_0.JPG
307 ms
IMG_0833.jpg
308 ms
193Gray.jpg
324 ms
IMG_8521_0.JPG
326 ms
01%20Jan%2012%202016%20Broxburn%20%283%29.JPG
356 ms
39Vaughan.jpg
357 ms
feed-icon.png
358 ms
logo_LTN.png
423 ms
87 ms
loader0.js
99 ms
46 ms
7916-931-10-6137.js
30 ms
c
291 ms
collect
13 ms
application2.js
109 ms
grapevine.ca accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
grapevine.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
grapevine.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grapevine.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Grapevine.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.
grapevine.ca
Open Graph description is not detected on the main page of Grapevine. 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: