Tools & Wizards About Us
calliaflowers.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

calliaflowers.com

Best Experience Sending Flowers & Gifts in Canada & the US | Callia

Page Load Speed

842 ms in total

First Response

25 ms

Resources Loaded

768 ms

Page Rendered

49 ms

calliaflowers.com screenshot

About Website

Click here to check amazing Callia Flowers content for Canada. Otherwise, check out these important facts you probably never knew about calliaflowers.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 calliaflowers.com

Key Findings

We analyzed Calliaflowers.com page load time and found that the first response time was 25 ms and then it took 817 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

calliaflowers.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value1,490 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value1.061

2/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

calliaflowers.com

25 ms

callia.com

27 ms

callia.com

175 ms

gtm.js

105 ms

124297.ct.js

70 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Calliaflowers.com, 68% (23 requests) were made to Callia.com and 9% (3 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (540 ms) relates to the external source Callia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.1 kB (16%)

Content Size

959.5 kB

After Optimization

805.4 kB

  • HTML
  • JavaScript

In fact, the total size of Calliaflowers.com main page is 959.5 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. 25% of websites need less resources to load. Javascripts take 951.5 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 4.8 kB

  • Original 8.0 kB
  • After minification 7.9 kB
  • After compression 3.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 4.8 kB or 60% of the original size.

JavaScript Optimization

-16%

Potential reduce by 149.3 kB

  • Original 951.5 kB
  • After minification 951.5 kB
  • After compression 802.2 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 149.3 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (89%)

Requests Now

28

After Optimization

3

  • AJAX
  • JavaScript

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Callia Flowers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

calliaflowers.com

calliaflowers.com

25 ms

callia.com

callia.com

27 ms

callia.com

callia.com

175 ms

gtm.js

gtm.js

105 ms

124297.ct.js

124297.ct.js

70 ms

datadog-rum-v4.js

datadog-rum-v4.js

39 ms

model

model

46 ms

event

event

110 ms

dot.txt

dot.txt

57 ms

polyfill.js

polyfill.js

6 ms

js

js

77 ms

ad73e3b.js

ad73e3b.js

136 ms

66d270b.js

66d270b.js

153 ms

f91f988.js

f91f988.js

191 ms

bae2fdf.js

bae2fdf.js

158 ms

4af93c8.js

4af93c8.js

164 ms

d43f597.js

d43f597.js

176 ms

351bbda.js

351bbda.js

255 ms

32d195f.js

32d195f.js

278 ms

b5c51a6.js

b5c51a6.js

267 ms

b56305c.js

b56305c.js

288 ms

bf76756.js

bf76756.js

299 ms

1f31b3b.js

1f31b3b.js

398 ms

243201b.js

243201b.js

405 ms

c2ef198.js

c2ef198.js

418 ms

828c450.js

828c450.js

420 ms

8df4a0d.js

8df4a0d.js

415 ms

3806745.js

3806745.js

429 ms

cf73d77.js

cf73d77.js

532 ms

39bb6ee.js

39bb6ee.js

522 ms

0348ba3.js

0348ba3.js

540 ms

2e46034.js

2e46034.js

530 ms

places.js

places.js

5 ms

main.js

main.js

10 ms

Accessibility Review

calliaflowers.com accessibility score

56

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

ARIA IDs are not unique

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

High

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

calliaflowers.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

calliaflowers.com SEO score

97

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Calliaflowers.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 Calliaflowers.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.

Social Sharing Optimization

calliaflowers.com

Open Graph description is not detected on the main page of Callia Flowers. 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: