Tools & Wizards About Us
florganic.com.mx screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

florganic.com.mx

Envía flores, regalos y globos a domicilio - Florganic flores a domicilio DF

Page Load Speed

3.5 sec in total

First Response

441 ms

Resources Loaded

2.7 sec

Page Rendered

329 ms

florganic.com.mx screenshot

About Website

Visit florganic.com.mx now to see the best up-to-date Florganic content for Mexico and also check out these interesting facts you probably never knew about florganic.com.mx

Entregas GRATIS, mismo día. Envía ramos de flores, regalos a domicilio 2017. Pago seguro y fácil. MESES SIN INTERESES. 57409478 en CDMX y Área Metr.

Visit florganic.com.mx

Key Findings

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

Performance Metrics

florganic.com.mx performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.994

2/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

www.florganic.com.mx

441 ms

main.css

69 ms

layout.css

72 ms

font.css

73 ms

web.js.81df69f80213857d0c7a.js

135 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Florganic.com.mx, 29% (22 requests) were made to Image.jimcdn.com and 13% (10 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (441 ms) belongs to the original domain Florganic.com.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 627.1 kB (49%)

Content Size

1.3 MB

After Optimization

645.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Florganic.com.mx main page is 1.3 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. Javascripts take 635.8 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 58.6 kB

  • Original 82.2 kB
  • After minification 79.8 kB
  • After compression 23.6 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 58.6 kB or 71% of the original size.

Image Optimization

-1%

Potential reduce by 3.9 kB

  • Original 356.0 kB
  • After minification 352.0 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. Florganic images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 415.4 kB

  • Original 635.8 kB
  • After minification 635.8 kB
  • After compression 220.4 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 415.4 kB or 65% of the original size.

CSS Optimization

-75%

Potential reduce by 149.1 kB

  • Original 198.3 kB
  • After minification 198.0 kB
  • After compression 49.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. Florganic.com.mx needs all CSS files to be minified and compressed as it can save up to 149.1 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (48%)

Requests Now

73

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.florganic.com.mx

www.florganic.com.mx

441 ms

main.css

main.css

69 ms

layout.css

layout.css

72 ms

font.css

font.css

73 ms

web.js.81df69f80213857d0c7a.js

web.js.81df69f80213857d0c7a.js

135 ms

plusone.js

plusone.js

36 ms

image.jpg

image.jpg

225 ms

rlinkB.png

rlinkB.png

41 ms

header.jpg

header.jpg

14 ms

env%C3%ADa-flores-ramos-de-rosas-arreglos-florales-ramos-de-flores.jpg

env%C3%ADa-flores-ramos-de-rosas-arreglos-florales-ramos-de-flores.jpg

294 ms

image.jpg

image.jpg

245 ms

image.jpg

image.jpg

249 ms

image.jpg

image.jpg

266 ms

image.jpg

image.jpg

246 ms

image.jpg

image.jpg

249 ms

image.jpg

image.jpg

265 ms

image.jpg

image.jpg

266 ms

image.jpg

image.jpg

267 ms

image.jpg

image.jpg

267 ms

image.jpg

image.jpg

295 ms

image.jpg

image.jpg

291 ms

image.jpg

image.jpg

307 ms

image.jpg

image.jpg

293 ms

image.jpg

image.jpg

293 ms

image.jpg

image.jpg

305 ms

image.jpg

image.jpg

305 ms

image.jpg

image.jpg

321 ms

image.jpg

image.jpg

306 ms

image.jpg

image.jpg

320 ms

ramos-de-novia.jpg

ramos-de-novia.jpg

322 ms

d93e757e1104.png

d93e757e1104.png

18 ms

web_oldtemplate.css.2d44259dc7097634303898168c3a0804.css

web_oldtemplate.css.2d44259dc7097634303898168c3a0804.css

22 ms

ea80ec5a2c965c54340a933005e22d9d.woff

ea80ec5a2c965c54340a933005e22d9d.woff

34 ms

plusone.js

plusone.js

84 ms

all.js

all.js

223 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

42 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

38 ms

fastbutton

fastbutton

104 ms

birds.png

birds.png

14 ms

postmessageRelay

postmessageRelay

108 ms

ga.js

ga.js

53 ms

analytics.js

analytics.js

95 ms

loginstate

loginstate

358 ms

fastbutton

fastbutton

97 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

25 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

24 ms

__utm.gif

__utm.gif

60 ms

__utm.gif

__utm.gif

79 ms

__utm.gif

__utm.gif

231 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

68 ms

rpc:shindig_random.js

rpc:shindig_random.js

57 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

182 ms

collect

collect

31 ms

236 ms

xd_arbiter.php

xd_arbiter.php

207 ms

xd_arbiter.php

xd_arbiter.php

368 ms

widget_v2.134.js

widget_v2.134.js

29 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

153 ms

__$$__stringtable_lang_es.js

__$$__stringtable_lang_es.js

48 ms

collect

collect

15 ms

ping

ping

58 ms

collect

collect

4 ms

page.php

page.php

101 ms

Ezryo55Cca5.css

Ezryo55Cca5.css

178 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

254 ms

YvxwM8R7ol8.js

YvxwM8R7ol8.js

368 ms

ihptErjAmMX.js

ihptErjAmMX.js

336 ms

10422198_864380550354505_6695300629450226847_n.jpg

10422198_864380550354505_6695300629450226847_n.jpg

174 ms

12088170_794523864006841_8339636314418157652_n.jpg

12088170_794523864006841_8339636314418157652_n.jpg

213 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

47 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

47 ms

R9a_DtVRZgv.js

R9a_DtVRZgv.js

392 ms

cUDgRFxaoIk.js

cUDgRFxaoIk.js

391 ms

0JBr1QHp8Gi.js

0JBr1QHp8Gi.js

392 ms

kDOzhTr2W91.js

kDOzhTr2W91.js

391 ms

avatar_simple_visitor.png

avatar_simple_visitor.png

64 ms

Accessibility Review

florganic.com.mx accessibility score

74

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

Links do not have a discernible name

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

florganic.com.mx 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

florganic.com.mx 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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Florganic.com.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Florganic.com.mx 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

florganic.com.mx

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