1.5 sec in total
189 ms
1.1 sec
191 ms
Click here to check amazing Regal Florist content for Canada. Otherwise, check out these important facts you probably never knew about regalflorist.ca
Regal Florist, Garden Center, NOTL specializing in bridal, wedding, sympathy and event flowers. We offer a beautiful selection of home and garden decor, statues, fountains, seasonal plants and tropica...
Visit regalflorist.caWe analyzed Regalflorist.ca page load time and found that the first response time was 189 ms and then it took 1.3 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.
regalflorist.ca performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value4.2 s
45/100
25%
Value2.5 s
98/100
10%
Value230 ms
86/100
30%
Value0.357
30/100
15%
Value4.7 s
80/100
10%
189 ms
101 ms
100 ms
7 ms
110 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 97% of them (86 requests) were addressed to the original Regalflorist.ca, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (422 ms) belongs to the original domain Regalflorist.ca.
Page size can be reduced by 89.3 kB (11%)
801.6 kB
712.3 kB
In fact, the total size of Regalflorist.ca main page is 801.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 722.6 kB which makes up the majority of the site volume.
Potential reduce by 38.1 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 38.1 kB or 87% of the original size.
Potential reduce by 37.6 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. Regal Florist images are well optimized though.
Potential reduce by 12.0 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 12.0 kB or 36% of the original size.
Potential reduce by 1.6 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. Regalflorist.ca needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 77% of the original size.
Number of requests can be reduced by 3 (3%)
88
85
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Regal Florist. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
regalflorist.ca
189 ms
cbcscb2horizontt2010_files.css
101 ms
google_analytics_auto.js
100 ms
jquery-latest.min.js
7 ms
cbjscb2horizontt2010_files.js
110 ms
ga.js
23 ms
valentinesday.jpg
303 ms
words.jpg
47 ms
ebbtcb2horizontt2010_files1_0.gif
74 ms
ebbtcb2horizontt2010_files2_0.gif
86 ms
ebbtcb2horizontt2010_files3_0.gif
86 ms
ebbtcb2horizontt2010_files4_0.gif
88 ms
ebbtcb2horizontt2010_files5_0.gif
91 ms
ebbtcb2horizontt2010_files6_0.gif
120 ms
ebbtcb2horizontt2010_files7_0.gif
134 ms
ebbtcb2horizontt2010_files8_0.gif
140 ms
ebbtcb2horizontt2010_files9_0.gif
134 ms
ebbtcb2horizontt2010_files10_0.gif
141 ms
ebbtcb2horizontt2010_files11_0.gif
165 ms
new-15.jpg
223 ms
new-13.jpg
226 ms
new-11.jpg
352 ms
new-9.jpg
311 ms
new-10.jpg
209 ms
new-12.jpg
295 ms
new-14.jpg
385 ms
new-16.jpg
270 ms
fwlogo.jpg
325 ms
__utm.gif
25 ms
social.html
325 ms
ebbtcb2horizontt2010_files1_1.gif
307 ms
ebbtcb2horizontt2010_files1_2.gif
331 ms
ebbtcb2horizontt2010_files2_1.gif
332 ms
ebbtcb2horizontt2010_files2_2.gif
352 ms
ebbtcb2horizontt2010_files3_1.gif
358 ms
ebbtcb2horizontt2010_files3_2.gif
367 ms
ebbtcb2horizontt2010_files4_1.gif
371 ms
ebbtcb2horizontt2010_files4_2.gif
379 ms
ebbtcb2horizontt2010_files5_1.gif
398 ms
ebbtcb2horizontt2010_files5_2.gif
402 ms
ebbtcb2horizontt2010_files6_1.gif
408 ms
ebbtcb2horizontt2010_files6_2.gif
415 ms
ebbtcb2horizontt2010_files7_1.gif
416 ms
ebbtcb2horizontt2010_files7_2.gif
422 ms
ebbtcb2horizontt2010_files8_1.gif
415 ms
ebbtcb2horizontt2010_files8_2.gif
407 ms
ebbtcb2horizontt2010_files9_1.gif
410 ms
ebbtcb2horizontt2010_files9_2.gif
420 ms
ebbtcb2horizontt2010_files10_1.gif
418 ms
ebbtcb2horizontt2010_files10_2.gif
393 ms
ebbtcb2horizontt2010_files11_1.gif
398 ms
ebbtcb2horizontt2010_files11_2.gif
403 ms
wicker2.jpg
400 ms
cbsiicb2horizontt2010_files_1.gif
418 ms
cbsiicb2horizontt2010_files_2.gif
393 ms
cbsiicb2horizontt2010_files_3.gif
349 ms
cbsiicb2horizontt2010_files_4.gif
351 ms
cbsiicb2horizontt2010_files_5.gif
356 ms
cbsiicb2horizontt2010_files_6.gif
312 ms
cbsiicb2horizontt2010_files_7.gif
307 ms
cbsiicb2horizontt2010_files_8.gif
303 ms
cbsiicb2horizontt2010_files_9.gif
293 ms
cbsiicb2horizontt2010_files_10.gif
294 ms
cbsiicb2horizontt2010_files_11.gif
281 ms
cbsiicb2horizontt2010_files_12.gif
276 ms
cbsiicb2horizontt2010_files_13.gif
279 ms
cbsiicb2horizontt2010_files_14.gif
279 ms
cbsiicb2horizontt2010_files_15.gif
278 ms
cbsiicb2horizontt2010_files_16.gif
278 ms
cbsiicb2horizontt2010_files_17.gif
282 ms
cbsiicb2horizontt2010_files_18.gif
278 ms
cbsiicb2horizontt2010_files_19.gif
285 ms
cbsiicb2horizontt2010_files_20.gif
291 ms
cbsiicb2horizontt2010_files_21.gif
275 ms
cbsiicb2horizontt2010_files_22.gif
269 ms
cbsiicb2horizontt2010_files_23.gif
277 ms
cbsiicb2horizontt2010_files_24.gif
273 ms
cbsiicb2horizontt2010_files_25.gif
282 ms
cbsiicb2horizontt2010_files_26.gif
283 ms
cbsiicb2horizontt2010_files_27.gif
282 ms
cbsiicb2horizontt2010_files_28.gif
265 ms
cbsiicb2horizontt2010_files_29.gif
277 ms
cbsiicb2horizontt2010_files_30.gif
272 ms
cbsiicb2horizontt2010_files_31.gif
280 ms
flyFacebook.png
299 ms
flypinit.png
304 ms
flyInstagram.png
278 ms
flygoogle.png
294 ms
flyemail.png
280 ms
regalflorist.ca 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
regalflorist.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
regalflorist.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
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Regalflorist.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Regalflorist.ca main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
regalflorist.ca
Open Graph description is not detected on the main page of Regal Florist. 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: