3.6 sec in total
244 ms
3 sec
345 ms
Visit vancouverrosesociety.org now to see the best up-to-date Vancouver Rose Society content and also check out these interesting facts you probably never knew about vancouverrosesociety.org
Since 1949, Vancouver Rose Society members have been growing roses, sharing garden tips, enjoying guest speakers, exhibiting roses, forming friendships, and visiting each others� gardens.
Visit vancouverrosesociety.orgWe analyzed Vancouverrosesociety.org page load time and found that the first response time was 244 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
vancouverrosesociety.org performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value15.8 s
0/100
25%
Value5.4 s
57/100
10%
Value110 ms
98/100
30%
Value0.03
100/100
15%
Value5.5 s
70/100
10%
244 ms
42 ms
55 ms
63 ms
1973 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Vancouverrosesociety.org, 38% (15 requests) were made to Img-fl.nccdn.net and 38% (15 requests) were made to 0201.nccdn.net. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Img-fl.nccdn.net.
Page size can be reduced by 208.2 kB (11%)
1.8 MB
1.6 MB
In fact, the total size of Vancouverrosesociety.org main page is 1.8 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. 55% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 131.7 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 131.7 kB or 87% of the original size.
Potential reduce by 76.3 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. Vancouver Rose Society images are well optimized though.
Potential reduce by 226 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 19 B
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. Vancouverrosesociety.org has all CSS files already compressed.
Number of requests can be reduced by 18 (49%)
37
19
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vancouver Rose Society. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
vancouverrosesociety.org
244 ms
react.production.min.js
42 ms
react-dom.production.min.js
55 ms
fat_core.EN.js
63 ms
env.js
1973 ms
fat_eua.EN.js
67 ms
fat_freemona.css
66 ms
js
124 ms
fat_freemona.js
61 ms
fat_display.EN.js
46 ms
fat_display.js
46 ms
fat_display_item.js
49 ms
styles.css
53 ms
fat_slideshow_animated.EN.js
36 ms
fat_display.js
38 ms
fat_display.EN.js
36 ms
fat_display.js
39 ms
fat_styles.css
47 ms
css
31 ms
headerlogoi.png
89 ms
blank.gif
41 ms
home_3squares_rosecareimage.png
386 ms
home_3squares_whichrose.png
283 ms
home_3squares_forournextmeeting.png
355 ms
footerlogo.png
241 ms
fb.png
263 ms
ig.png
106 ms
askjoinus_bgimage_1.jpg
96 ms
shadow-up.png
107 ms
js
131 ms
analytics.js
47 ms
84dfb7e54ac44355a1629ec1afc3a169.png
104 ms
nav-button-left.png
149 ms
nav-button-right.png
259 ms
whitebg.png
641 ms
thinpinkline.png
314 ms
collect
44 ms
texture-sections-bevel.png
281 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSo3Sup5.ttf
47 ms
vancouverrosesociety.org accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
vancouverrosesociety.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
vancouverrosesociety.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vancouverrosesociety.org 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 Vancouverrosesociety.org 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.
vancouverrosesociety.org
Open Graph data is detected on the main page of Vancouver Rose Society. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: