Tools & Wizards About Us
iflowers.com screenshot

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

iflowers.com

VIRTUAL FLOWERS and FREE E-CARDS at iFlowers® - Order Flowers Online

Page Load Speed

596 ms in total

First Response

93 ms

Resources Loaded

331 ms

Page Rendered

172 ms

iflowers.com screenshot

About Website

Welcome to iflowers.com homepage info - get ready to check IFlowers best content for United States right away, or after learning these important things about iflowers.com

Send Free Virtual Flowers, Bouquets and e-Cards to anyone on the Internet, or order flowers online, at iFlowers Virtual Florist.

Visit iflowers.com

Key Findings

We analyzed Iflowers.com page load time and found that the first response time was 93 ms and then it took 503 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

iflowers.com performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value0.8 s

100/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value0.9 s

100/100

10%

Network Requests Diagram

iflowers.com

93 ms

sharethis.js

10 ms

sharethis.1ac33bc7d4476110a610f925104446ff.css

12 ms

120x90.gif

83 ms

ilogosm.gif

87 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 38% of them (15 requests) were addressed to the original Iflowers.com, 10% (4 requests) were made to W.sharethis.com and 10% (4 requests) were made to 800florals.com. The less responsive or slowest element that took the longest time to load (166 ms) relates to the external source 800florals.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 149.5 kB (62%)

Content Size

241.0 kB

After Optimization

91.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 17.3 kB

  • Original 21.3 kB
  • After minification 16.8 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. This page needs HTML code to be minified as it can gain 4.5 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.3 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 662 B

  • Original 43.5 kB
  • After minification 42.8 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. IFlowers images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 130.0 kB

  • Original 174.1 kB
  • After minification 174.1 kB
  • After compression 44.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 130.0 kB or 75% of the original size.

CSS Optimization

-71%

Potential reduce by 1.6 kB

  • Original 2.2 kB
  • After minification 2.2 kB
  • After compression 625 B

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. Iflowers.com needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (26%)

Requests Now

34

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iflowers.com

iflowers.com

93 ms

sharethis.js

sharethis.js

10 ms

sharethis.1ac33bc7d4476110a610f925104446ff.css

sharethis.1ac33bc7d4476110a610f925104446ff.css

12 ms

120x90.gif

120x90.gif

83 ms

ilogosm.gif

ilogosm.gif

87 ms

butn1.gif

butn1.gif

85 ms

NewFlwrsbttn.GIF

NewFlwrsbttn.GIF

81 ms

rosebutn.gif

rosebutn.gif

83 ms

butn2.gif

butn2.gif

84 ms

studio-butn1.gif

studio-butn1.gif

83 ms

butn3.gif

butn3.gif

85 ms

butn10.gif

butn10.gif

85 ms

butn8.gif

butn8.gif

86 ms

butn4.gif

butn4.gif

85 ms

vif7-sm.jpg

vif7-sm.jpg

86 ms

TFDRVsm.jpg

TFDRVsm.jpg

162 ms

TV317sm.jpg

TV317sm.jpg

161 ms

P420Xsm.jpg

P420Xsm.jpg

143 ms

P310Xsm.jpg

P310Xsm.jpg

166 ms

iFlowerlink1.gif

iFlowerlink1.gif

84 ms

getSegment.php

getSegment.php

16 ms

index.a8fc48294ca4cc10eb440189d9f22d7c.html

index.a8fc48294ca4cc10eb440189d9f22d7c.html

19 ms

bg-wave.gif

bg-wave.gif

20 ms

share-icon-16x16.png

share-icon-16x16.png

10 ms

t.dhj

t.dhj

9 ms

st.125da8bfe70ad3e00a35a6e4c65d8bc5.js

st.125da8bfe70ad3e00a35a6e4c65d8bc5.js

17 ms

t.dhj

t.dhj

9 ms

x35248

x35248

116 ms

pixel

pixel

16 ms

s-3271.xgi

s-3271.xgi

5 ms

hbpix

hbpix

68 ms

6 ms

pixel

pixel

13 ms

xrefid.xgi

xrefid.xgi

6 ms

7 ms

cm

cm

8 ms

pixel

pixel

15 ms

pixel

pixel

14 ms

2981

2981

22 ms

Accessibility Review

iflowers.com accessibility score

93

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

iflowers.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

iflowers.com SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iflowers.com 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 Iflowers.com main page’s claimed encoding is iso-8859-1. 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.

Social Sharing Optimization

iflowers.com

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