5.8 sec in total
77 ms
5.1 sec
624 ms
Visit bitafloral.ca now to see the best up-to-date Bitafloral content and also check out these interesting facts you probably never knew about bitafloral.ca
Want to send a smile without saying a word? Why not send a bouquet of beautiful flowers? Order now for fast and easy delivery.
Visit bitafloral.caWe analyzed Bitafloral.ca page load time and found that the first response time was 77 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
bitafloral.ca performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value23.6 s
0/100
25%
Value21.5 s
0/100
10%
Value8,670 ms
0/100
30%
Value0.091
92/100
15%
Value26.3 s
0/100
10%
77 ms
1874 ms
30 ms
47 ms
50 ms
Our browser made a total of 185 requests to load all elements on the main page. We found that 94% of them (173 requests) were addressed to the original Bitafloral.ca, 4% (8 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Bitafloral.ca.
Page size can be reduced by 988.8 kB (27%)
3.6 MB
2.6 MB
In fact, the total size of Bitafloral.ca main page is 3.6 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. Only a small number of websites need less resources to load. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 354.2 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 354.2 kB or 87% of the original size.
Potential reduce by 21.9 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. Bitafloral images are well optimized though.
Potential reduce by 511.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 511.4 kB or 26% of the original size.
Potential reduce by 101.4 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. Bitafloral.ca needs all CSS files to be minified and compressed as it can save up to 101.4 kB or 22% of the original size.
Number of requests can be reduced by 156 (93%)
167
11
The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bitafloral. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 108 to 1 for JavaScripts and from 50 to 1 for CSS and as a result speed up the page load time.
bitafloral.ca
77 ms
bitafloral.ca
1874 ms
swpb-front-end.css
30 ms
style.css
47 ms
jquery.selectBox.css
50 ms
font-awesome.css
50 ms
prettyPhoto.css
56 ms
style.css
52 ms
styles.css
54 ms
countdown-timer-widget.css
58 ms
menu-image.css
61 ms
dashicons.css
83 ms
woocommerce-layout.css
67 ms
woocommerce.css
69 ms
public-clean.css
75 ms
public-main.css
77 ms
frontend.css
78 ms
style.css
84 ms
style.css
85 ms
elementor-icons.css
86 ms
frontend.css
89 ms
swiper.css
101 ms
post-4.css
103 ms
frontend.css
128 ms
global.css
105 ms
post-1766.css
103 ms
post-1640.css
108 ms
post-1523.css
109 ms
post-10629.css
110 ms
post-10611.css
118 ms
sv-wc-payment-gateway-payment-form.min.css
117 ms
wc-moneris.min.css
118 ms
front.css
119 ms
yith-icon.css
123 ms
color-picker.css
148 ms
photobox.css
149 ms
shortcodes.css
151 ms
css
35 ms
chkt_v1.00.js
303 ms
api.js
41 ms
style.css
143 ms
font-awesome.min.css
140 ms
bootstrap.min.css
126 ms
rtl.css
136 ms
jquery.fancybox.css
135 ms
app-red.css
150 ms
app-responsive.css
131 ms
style.css
136 ms
fontawesome.css
134 ms
solid.css
138 ms
wc-blocks.css
130 ms
animations.min.css
199 ms
rs6.css
198 ms
jquery.js
215 ms
jquery-migrate.js
194 ms
wp-polyfill-inert.js
188 ms
regenerator-runtime.js
188 ms
wp-polyfill.js
236 ms
hooks.js
233 ms
frontend.js
219 ms
jquery.blockUI.js
221 ms
add-to-cart.js
217 ms
js.cookie.js
244 ms
woocommerce.js
245 ms
react-refresh-runtime.js
243 ms
react-refresh-entry.js
244 ms
public-time.js
252 ms
public-blazy.min.js
246 ms
public-main.js
246 ms
underscore.min.js
246 ms
wp-util.js
250 ms
jquery.selectBox.min.js
349 ms
jquery.prettyPhoto.js
326 ms
jquery.yith-wcwl.js
324 ms
index.js
319 ms
index.js
319 ms
jquery.countdownTimer.js
316 ms
rbtools.min.js
521 ms
rs6.min.js
528 ms
sourcebuster.js
520 ms
order-attribution.js
515 ms
react.js
519 ms
deprecated.js
507 ms
dom.js
506 ms
react-dom.js
514 ms
escape-html.js
512 ms
element.js
445 ms
is-shallow-equal.js
441 ms
i18n.js
441 ms
keycodes.js
442 ms
priority-queue.js
444 ms
compose.js
445 ms
private-apis.js
401 ms
redux-routine.js
399 ms
data.js
399 ms
lodash.js
404 ms
wc-blocks-registry.js
371 ms
url.js
372 ms
api-fetch.js
370 ms
wc-settings.js
369 ms
data-controls.js
372 ms
html-entities.js
365 ms
notices.js
363 ms
wc-blocks-middleware.js
363 ms
wc-blocks-data.js
358 ms
dom-ready.js
258 ms
a11y.js
258 ms
primitives.js
258 ms
warning.js
258 ms
blocks-components.js
258 ms
blocks-checkout.js
259 ms
order-attribution-blocks.js
259 ms
api-request.js
52 ms
frontend.js
50 ms
isotope.js
51 ms
portfolio.js
51 ms
script.js
51 ms
sw_woocommerce_search_products.min.js
52 ms
jquery.payment.js
50 ms
sv-wc-payment-gateway-payment-form.js
47 ms
wc-moneris.min.js
48 ms
core.js
50 ms
mouse.js
47 ms
draggable.js
49 ms
slider.js
51 ms
jquery.ui.touch-punch.js
50 ms
iris.min.js
48 ms
color-picker.min.js
49 ms
datepicker.js
75 ms
progressbar.js
74 ms
add-to-cart-variation.js
76 ms
front.js
73 ms
index.js
72 ms
jquery.flexslider-min.js
73 ms
photobox.js
579 ms
jquery.classycountdown.min.js
578 ms
smush-lazy-load.min.js
577 ms
slick.min.js
575 ms
jquery.countdown.min.js
575 ms
editor.js
573 ms
bootstrap.min.js
577 ms
plugins.js
577 ms
main.js
577 ms
jquery.fancybox.pack.js
576 ms
quickview.js
574 ms
wc-quantity-increment.min.js
575 ms
megamenu.js
576 ms
category-ajax.js
574 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf
58 ms
0QI6MX1D_JOuGQbT0gvTJPa787wsuxJBkqg.ttf
59 ms
0QI6MX1D_JOuGQbT0gvTJPa787zAvBJBkqg.ttf
565 ms
0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqg.ttf
567 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mQ.ttf
566 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-PgFoq92mQ.ttf
567 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-BQCoq92mQ.ttf
568 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-C0Coq92mQ.ttf
566 ms
cart-fragments.js
566 ms
single-product.js
564 ms
webpack-pro.runtime.js
564 ms
webpack.runtime.js
563 ms
frontend-modules.js
563 ms
frontend.js
563 ms
waypoints.js
562 ms
frontend.js
562 ms
elements-handlers.js
561 ms
frontend.min.js
560 ms
BitterRegular.woff
560 ms
fa-solid-900.woff
562 ms
LoraItalic.woff
556 ms
fontawesome-webfont.woff
556 ms
fontawesome-webfont.woff
556 ms
fontawesome-webfont.woff
532 ms
eicons.woff
529 ms
istockphoto-1397914849-2048x2048-1-1024x683.jpg
527 ms
guest.png
530 ms
banne.png
678 ms
2024-01-23-13.01.54.jpg
680 ms
fontawesome-webfont.ttf
213 ms
recaptcha__en.js
476 ms
logo.webp
301 ms
birtyday-260x260.png
301 ms
bitafloral.ca
892 ms
2024-01-23-13.01.54-600x800.jpg
50 ms
Field-Of-Innocence-PhotoRoom-1.png
34 ms
woocommerce-smallscreen.css
17 ms
bitafloral.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
Image elements do not have [alt] attributes
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
bitafloral.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
Missing source maps for large first-party JavaScript
bitafloral.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Bitafloral.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 Bitafloral.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.
bitafloral.ca
Open Graph data is detected on the main page of Bitafloral. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: