2.3 sec in total
14 ms
2.2 sec
67 ms
Click here to check amazing Callia content for Canada. Otherwise, check out these important facts you probably never knew about callia.com
Rated 4.9/5 stars. Loved by 300,000+ people. Order fast, easy & same day picture-perfect bouquets exactly like the photo. Always fresh, on-time & guaranteed. Shop now.
Visit callia.comWe analyzed Callia.com page load time and found that the first response time was 14 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
callia.com performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value14.2 s
0/100
25%
Value9.8 s
10/100
10%
Value1,550 ms
13/100
30%
Value0.868
4/100
15%
Value14.2 s
9/100
10%
14 ms
1506 ms
139 ms
209 ms
110 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 48% of them (22 requests) were addressed to the original Callia.com, 7% (3 requests) were made to Clarity.ms and 7% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Callia.com.
Page size can be reduced by 12.1 kB (3%)
445.7 kB
433.6 kB
In fact, the total size of Callia.com main page is 445.7 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. 65% of websites need less resources to load. Javascripts take 432.4 kB which makes up the majority of the site volume.
Potential reduce by 8.5 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 8.5 kB or 64% of the original size.
Potential reduce by 3.6 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 36 (84%)
43
7
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Callia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and as a result speed up the page load time.
callia.com
14 ms
callia.com
1506 ms
gtm.js
139 ms
js
209 ms
bat.js
110 ms
124297.ct.js
113 ms
datadog-rum-v4.js
109 ms
fbevents.js
75 ms
loader.js
112 ms
model
109 ms
event
136 ms
dot.txt
109 ms
polyfill.js
295 ms
js
133 ms
b0eb33b.js
167 ms
922d2b9.js
245 ms
05aa508.js
292 ms
51cad88.js
242 ms
3c8f948.js
247 ms
fdff9b1.js
203 ms
5ba86bf.js
292 ms
018c614.js
456 ms
ec31655.js
316 ms
13b60ef.js
325 ms
b2d37bb.js
371 ms
7440734.js
493 ms
4bbeca8.js
396 ms
fd608fe.js
432 ms
248eac8.js
439 ms
7c01652.js
475 ms
0ec2179.js
540 ms
b457409.js
538 ms
15c0922.js
558 ms
6ba26cd.js
598 ms
134615381.js
15 ms
134615381
83 ms
js
66 ms
pixel.js
49 ms
clarity.js
43 ms
rp.gif
29 ms
t2_eah697tl_telemetry
9 ms
aoacy2lr7v
36 ms
ld.js
25 ms
syncframe
20 ms
event
28 ms
c.gif
8 ms
callia.com 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
Form elements do not have associated labels
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.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
callia.com 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
callia.com SEO score
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 Callia.com 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 Callia.com 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.
callia.com
Open Graph description is not detected on the main page of Callia. 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: