Tools & Wizards About Us
florista.in screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

florista.in

Flowers to India, flowers online, Send roses online – florista-in

Page Load Speed

6.6 sec in total

First Response

1.7 sec

Resources Loaded

4.4 sec

Page Rendered

474 ms

florista.in screenshot

About Website

Welcome to florista.in homepage info - get ready to check Florista best content for India right away, or after learning these important things about florista.in

flowers to India, chocolates , cakes and gifts all India. Same Day delivery, All India flower delivery, flowers to Mumbai, flowers to Pune, Online flowers to Mumbai, Mumbai florist, florist in Mumbai,...

Visit florista.in

Key Findings

We analyzed Florista.in page load time and found that the first response time was 1.7 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

florista.in performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value450 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

www.florista.in

1729 ms

combinedCSS_190CE1F86FD769D29C062F8806931021.css

1098 ms

combinedJS_AD21F0024B1C333A110833A1FF8E14E0.js

2035 ms

WebResource.axd

434 ms

WebResource.axd

1087 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 15% of them (7 requests) were addressed to the original Florista.in, 59% (27 requests) were made to Cdn.florista.in and 13% (6 requests) were made to Cdn.florista.in.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Florista.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 788.8 kB (42%)

Content Size

1.9 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Florista.in main page is 1.9 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. 55% of websites need less resources to load. Images take 966.5 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 577.5 kB

  • Original 634.5 kB
  • After minification 557.9 kB
  • After compression 57.1 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 76.6 kB, which is 12% 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 577.5 kB or 91% of the original size.

Image Optimization

-1%

Potential reduce by 7.3 kB

  • Original 966.5 kB
  • After minification 959.2 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. Florista images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 114.1 kB

  • Original 161.8 kB
  • After minification 145.8 kB
  • After compression 47.7 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 114.1 kB or 71% of the original size.

CSS Optimization

-80%

Potential reduce by 89.9 kB

  • Original 112.1 kB
  • After minification 112.0 kB
  • After compression 22.2 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. Florista.in needs all CSS files to be minified and compressed as it can save up to 89.9 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (33%)

Requests Now

40

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.florista.in

www.florista.in

1729 ms

combinedCSS_190CE1F86FD769D29C062F8806931021.css

combinedCSS_190CE1F86FD769D29C062F8806931021.css

1098 ms

combinedJS_AD21F0024B1C333A110833A1FF8E14E0.js

combinedJS_AD21F0024B1C333A110833A1FF8E14E0.js

2035 ms

WebResource.axd

WebResource.axd

434 ms

WebResource.axd

WebResource.axd

1087 ms

combinedJS_3CD5135CDF8E44E498F8A582FBEEE575.js

combinedJS_3CD5135CDF8E44E498F8A582FBEEE575.js

231 ms

combinedJS_FFDED3A11125A4F887B66651574755F3.js

combinedJS_FFDED3A11125A4F887B66651574755F3.js

656 ms

proximanova.woff

proximanova.woff

801 ms

analytics.js

analytics.js

32 ms

scroll-to-top.png

scroll-to-top.png

61 ms

flsprites.png

flsprites.png

63 ms

footer-logo.png

footer-logo.png

62 ms

dlocation-dropdown.png

dlocation-dropdown.png

62 ms

search.png

search.png

62 ms

10d33586-3805-4d12-807f-7ec137cc2cba.jpg

10d33586-3805-4d12-807f-7ec137cc2cba.jpg

1026 ms

74e19e9c-2d5b-4ed9-a199-fec88a279530.jpg

74e19e9c-2d5b-4ed9-a199-fec88a279530.jpg

63 ms

5c8b4d04-0126-43e0-8305-3551ac5544c2.jpg

5c8b4d04-0126-43e0-8305-3551ac5544c2.jpg

65 ms

d1e6b96d-c0ff-4699-ae9d-1fc9da7a8077.jpg

d1e6b96d-c0ff-4699-ae9d-1fc9da7a8077.jpg

174 ms

9349be6a-835b-46c9-829c-1a36f0b85319.jpg

9349be6a-835b-46c9-829c-1a36f0b85319.jpg

66 ms

small-banner-bg.jpg

small-banner-bg.jpg

175 ms

same-day-dilivery.jpg

same-day-dilivery.jpg

176 ms

corporate-bg.jpg

corporate-bg.jpg

179 ms

floristasprites.png

floristasprites.png

177 ms

collect

collect

121 ms

cart.png

cart.png

497 ms

roboto-regular-webfont.woff

roboto-regular-webfont.woff

115 ms

Roboto-Bold-webfont.woff

Roboto-Bold-webfont.woff

115 ms

roboto-light-webfont.woff

roboto-light-webfont.woff

115 ms

WebRupee.V2.0.ttf

WebRupee.V2.0.ttf

116 ms

sdk.js

sdk.js

185 ms

FLO_058s.jpg

FLO_058s.jpg

474 ms

FLO_051s.jpg

FLO_051s.jpg

476 ms

FLO_129s.jpg

FLO_129s.jpg

478 ms

FLO_411s.jpg

FLO_411s.jpg

487 ms

3755dcec-3049-4211-b288-4b91a009c687.jpg

3755dcec-3049-4211-b288-4b91a009c687.jpg

476 ms

983246f5-4c45-43bb-b1db-4e1e47be47e7.jpg

983246f5-4c45-43bb-b1db-4e1e47be47e7.jpg

467 ms

banner-arrow-left.png

banner-arrow-left.png

79 ms

banner-arrow-right.png

banner-arrow-right.png

80 ms

slider-left.jpg

slider-left.jpg

79 ms

slider-right-default.jpg

slider-right-default.jpg

80 ms

ee6208e7-da02-44d8-aa36-3b06c433d5e5.png

ee6208e7-da02-44d8-aa36-3b06c433d5e5.png

80 ms

0e5f5d48-d785-4f21-8528-2c22e7f55d4a.png

0e5f5d48-d785-4f21-8528-2c22e7f55d4a.png

929 ms

7dbed24a-e9bd-4207-ab3a-d504aba02eb1.png

7dbed24a-e9bd-4207-ab3a-d504aba02eb1.png

80 ms

117 ms

xd_arbiter.php

xd_arbiter.php

128 ms

xd_arbiter.php

xd_arbiter.php

260 ms

Accessibility Review

florista.in accessibility score

67

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-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

florista.in best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

florista.in SEO score

91

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

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

    N/A

  • Encoding

    UTF-8

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

florista.in

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