Tools & Wizards About Us
xpressflora.com screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

xpressflora.com

Best online flowers & Cake delivery - Send Gifts to your dearest one

Page Load Speed

7.9 sec in total

First Response

860 ms

Resources Loaded

6.5 sec

Page Rendered

589 ms

xpressflora.com screenshot

About Website

Visit xpressflora.com now to see the best up-to-date Xpressflora content for India and also check out these interesting facts you probably never knew about xpressflora.com

Best Online Flowers , Cake Delivery & Most Trusted Indian Online Florist | Free Gifts Delivery to India at the Cheapest rate.Send gift to India online with high quality, best service and fast delivery...

Visit xpressflora.com

Key Findings

We analyzed Xpressflora.com page load time and found that the first response time was 860 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

xpressflora.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.137

79/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

xpressflora.com

860 ms

xpressflora.com

2858 ms

js

96 ms

modernizr-2.6.2.js

959 ms

bootstrap.css

1346 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 81% of them (63 requests) were addressed to the original Xpressflora.com, 17% (13 requests) were made to Embed.tawk.to and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Xpressflora.com.

Page Optimization Overview & Recommendations

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

Content Size

3.1 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xpressflora.com main page is 3.1 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. 60% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 217.1 kB

  • Original 254.8 kB
  • After minification 177.3 kB
  • After compression 37.7 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 77.5 kB, which is 30% 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 217.1 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 16.8 kB

  • Original 2.2 MB
  • After minification 2.1 MB

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. Xpressflora images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 369.6 kB

  • Original 581.4 kB
  • After minification 389.3 kB
  • After compression 211.8 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 369.6 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 125.3 kB

  • Original 146.2 kB
  • After minification 116.5 kB
  • After compression 20.9 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. Xpressflora.com needs all CSS files to be minified and compressed as it can save up to 125.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (29%)

Requests Now

73

After Optimization

52

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xpressflora.com

xpressflora.com

860 ms

xpressflora.com

xpressflora.com

2858 ms

js

js

96 ms

modernizr-2.6.2.js

modernizr-2.6.2.js

959 ms

bootstrap.css

bootstrap.css

1346 ms

Site.css

Site.css

977 ms

star-rating.min.css

star-rating.min.css

806 ms

jquery-1.8.2.js

jquery-1.8.2.js

23 ms

star-rating.min.js

star-rating.min.js

823 ms

MsAjaxJs

MsAjaxJs

796 ms

jquery-1.10.2.js

jquery-1.10.2.js

1847 ms

bootstrap.js

bootstrap.js

1057 ms

respond.js

respond.js

971 ms

WebFormsJs

WebFormsJs

973 ms

Logo2.png

Logo2.png

187 ms

header-user.png

header-user.png

193 ms

header-help.png

header-help.png

195 ms

call.png

call.png

204 ms

support.png

support.png

191 ms

MenuLink.png

MenuLink.png

373 ms

wait.gif

wait.gif

383 ms

SpecialFlower.jpg

SpecialFlower.jpg

576 ms

SpecialCake.jpg

SpecialCake.jpg

583 ms

ChokolateBouguets.jpg

ChokolateBouguets.jpg

610 ms

SpecialCombo.jpg

SpecialCombo.jpg

559 ms

UpcomingEvent1.jpg

UpcomingEvent1.jpg

1142 ms

UpcomingEvent2.jpg

UpcomingEvent2.jpg

746 ms

ProductFlower45.jpg

ProductFlower45.jpg

769 ms

ProductFlower24.jpg

ProductFlower24.jpg

779 ms

ProductFlower1.jpg

ProductFlower1.jpg

814 ms

ProductCombo15.jpg

ProductCombo15.jpg

851 ms

ProductCombo4.jpg

ProductCombo4.jpg

931 ms

ProductCake3.jpg

ProductCake3.jpg

961 ms

ProductCombo8.jpg

ProductCombo8.jpg

973 ms

ProductFlower46.jpg

ProductFlower46.jpg

1018 ms

ProductFlower60.jpg

ProductFlower60.jpg

1050 ms

ProductFlower59.jpg

ProductFlower59.jpg

1116 ms

ProductFlower58a.jpg

ProductFlower58a.jpg

1153 ms

ProductFlower57.jpg

ProductFlower57.jpg

1168 ms

ProductCake40.jpg

ProductCake40.jpg

1221 ms

ProductCake39.jpg

ProductCake39.jpg

1249 ms

ProductCake38.jpg

ProductCake38.jpg

1301 ms

ProductCake37.jpg

ProductCake37.jpg

1330 ms

Chocolate-40.jpg

Chocolate-40.jpg

1345 ms

Chocolate-39.jpg

Chocolate-39.jpg

1364 ms

Chocolate-38.jpg

Chocolate-38.jpg

1627 ms

Chocolate-37.jpg

Chocolate-37.jpg

1449 ms

ProductCombo52.jpg

ProductCombo52.jpg

1486 ms

ProductCombo51.jpg

ProductCombo51.jpg

1509 ms

ProductCombo50.jpg

ProductCombo50.jpg

1357 ms

ProductCombo49.jpg

ProductCombo49.jpg

1372 ms

Product-Special-07.jpg

Product-Special-07.jpg

1463 ms

ProductSpecial67.jpg

ProductSpecial67.jpg

1483 ms

ProductSpecial66.jpg

ProductSpecial66.jpg

1514 ms

ProductSpecial65.jpg

ProductSpecial65.jpg

1364 ms

facebook.png

facebook.png

1376 ms

twitter.png

twitter.png

1277 ms

googlePlus.png

googlePlus.png

1277 ms

Youtube.png

Youtube.png

1280 ms

instagram.png

instagram.png

1298 ms

pinpong.png

pinpong.png

1238 ms

default

default

162 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1206 ms

linkedin.png

linkedin.png

1270 ms

tumblr.png

tumblr.png

1272 ms

bg.png

bg.png

1233 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

73 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

63 ms

twk-event-polyfill.js

twk-event-polyfill.js

74 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

72 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

65 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

78 ms

twk-main.js

twk-main.js

75 ms

twk-vendor.js

twk-vendor.js

80 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

95 ms

twk-chunk-common.js

twk-chunk-common.js

87 ms

twk-runtime.js

twk-runtime.js

95 ms

twk-app.js

twk-app.js

86 ms

Accessibility Review

xpressflora.com accessibility score

66

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

Image elements do not have [alt] attributes

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.

Best Practices

xpressflora.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

xpressflora.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Xpressflora.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 Xpressflora.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

xpressflora.com

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