Tools & Wizards About Us
calliaflowers.com screenshot

Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

calliaflowers.com

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

Page Load Speed

949 ms in total

First Response

15 ms

Resources Loaded

870 ms

Page Rendered

64 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 15 ms and then it took 934 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

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value6,620 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.925

3/100

15%

TTI (Time to Interactive)

Value24.0 s

1/100

10%

Network Requests Diagram

calliaflowers.com

15 ms

callia.com

44 ms

callia.com

154 ms

gtm.js

109 ms

js

182 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Calliaflowers.com, 47% (22 requests) were made to Callia.com and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (579 ms) relates to the external source Callia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 155.0 kB (23%)

Content Size

668.7 kB

After Optimization

513.6 kB

  • HTML
  • JavaScript

In fact, the total size of Calliaflowers.com main page is 668.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 657.2 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 7.4 kB

  • Original 11.5 kB
  • After minification 11.4 kB
  • After compression 4.0 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 7.4 kB or 65% of the original size.

JavaScript Optimization

-22%

Potential reduce by 147.6 kB

  • Original 657.2 kB
  • After minification 657.0 kB
  • After compression 509.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 147.6 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (82%)

Requests Now

44

After Optimization

8

  • AJAX
  • Images
  • JavaScript

The browser has sent 44 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 37 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

calliaflowers.com

calliaflowers.com

15 ms

callia.com

callia.com

44 ms

callia.com

callia.com

154 ms

gtm.js

gtm.js

109 ms

js

js

182 ms

bat.js

bat.js

90 ms

124297.ct.js

124297.ct.js

90 ms

datadog-rum-v4.js

datadog-rum-v4.js

53 ms

fbevents.js

fbevents.js

60 ms

loader.js

loader.js

90 ms

polyfill.js

polyfill.js

60 ms

js

js

104 ms

67fbb71.js

67fbb71.js

133 ms

617abc1.js

617abc1.js

210 ms

77dd675.js

77dd675.js

174 ms

cf6a781.js

cf6a781.js

210 ms

ea97d45.js

ea97d45.js

216 ms

b135a89.js

b135a89.js

173 ms

67b5f98.js

67b5f98.js

319 ms

5813854.js

5813854.js

336 ms

c54ecec.js

c54ecec.js

344 ms

51e6aa7.js

51e6aa7.js

339 ms

678f31b.js

678f31b.js

346 ms

a9d3432.js

a9d3432.js

338 ms

1afe60b.js

1afe60b.js

401 ms

3f0e49b.js

3f0e49b.js

457 ms

55c4b8e.js

55c4b8e.js

469 ms

7f4d243.js

7f4d243.js

461 ms

ecc7a3f.js

ecc7a3f.js

468 ms

435682f.js

435682f.js

491 ms

46c0247.js

46c0247.js

528 ms

e4574b2.js

e4574b2.js

579 ms

134615381.js

134615381.js

14 ms

134615381

134615381

161 ms

js

js

115 ms

analytics.js

analytics.js

111 ms

pixel.js

pixel.js

154 ms

aoacy2lr7v

aoacy2lr7v

150 ms

clarity.js

clarity.js

56 ms

collect

collect

34 ms

rp.gif

rp.gif

22 ms

collect

collect

11 ms

ga-audiences

ga-audiences

29 ms

collect

collect

10 ms

ld.js

ld.js

18 ms

syncframe

syncframe

19 ms

c.gif

c.gif

7 ms

Accessibility Review

calliaflowers.com accessibility score

70

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

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

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 IDs are not unique

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

100

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

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: