Tools & Wizards About Us
florerialilly.com screenshot

Report Summary

  • 84

    Performance

    Renders faster than
    88% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

florerialilly.com

Florería Lilly | Ramos y Arreglos Florales para toda ocasión

Page Load Speed

3 sec in total

First Response

351 ms

Resources Loaded

2.4 sec

Page Rendered

244 ms

florerialilly.com screenshot

About Website

Visit florerialilly.com now to see the best up-to-date Floreria Lilly content and also check out these interesting facts you probably never knew about florerialilly.com

Productos | Floreria Lilly | Envio de flores, joyas y regalos para fechas especiales como: Dia de la Madre, Dia de los enamorados,nacimientos, cumpleaños, matrimonios, eventos a Lima Peru.

Visit florerialilly.com

Key Findings

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

Performance Metrics

florerialilly.com performance score

84

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.082

94/100

15%

TTI (Time to Interactive)

Value5.5 s

70/100

10%

Network Requests Diagram

florerialilly.com

351 ms

style.css

120 ms

principal.js

125 ms

api.js

50 ms

recaptcha__en.js

99 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 84% of them (62 requests) were addressed to the original Florerialilly.com, 5% (4 requests) were made to Google.com and 5% (4 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Florerialilly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 203.9 kB (47%)

Content Size

431.6 kB

After Optimization

227.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 18.7 kB

  • Original 23.4 kB
  • After minification 21.4 kB
  • After compression 4.8 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 18.7 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 318 B

  • Original 48.7 kB
  • After minification 48.4 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. Floreria Lilly images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 139.0 kB

  • Original 222.7 kB
  • After minification 222.3 kB
  • After compression 83.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 139.0 kB or 62% of the original size.

CSS Optimization

-34%

Potential reduce by 45.9 kB

  • Original 136.8 kB
  • After minification 136.0 kB
  • After compression 90.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. Florerialilly.com needs all CSS files to be minified and compressed as it can save up to 45.9 kB or 34% of the original size.

Requests Breakdown

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

Requests Now

67

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floreria Lilly. 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

florerialilly.com

florerialilly.com

351 ms

style.css

style.css

120 ms

principal.js

principal.js

125 ms

api.js

api.js

50 ms

recaptcha__en.js

recaptcha__en.js

99 ms

ga.js

ga.js

25 ms

spacer.gif

spacer.gif

103 ms

florerialilly_r1_c1.jpg

florerialilly_r1_c1.jpg

142 ms

florerialilly_r2_c1.jpg

florerialilly_r2_c1.jpg

102 ms

florerialilly_r2_c12.jpg

florerialilly_r2_c12.jpg

140 ms

florerialilly_r2_c13.jpg

florerialilly_r2_c13.jpg

140 ms

florerialilly_r3_c1.jpg

florerialilly_r3_c1.jpg

143 ms

florerialilly_r3_c2.jpg

florerialilly_r3_c2.jpg

152 ms

florerialilly_r3_c3.jpg

florerialilly_r3_c3.jpg

144 ms

florerialilly_r3_c4.jpg

florerialilly_r3_c4.jpg

218 ms

florerialilly_r3_c5.jpg

florerialilly_r3_c5.jpg

228 ms

florerialilly_r3_c6.jpg

florerialilly_r3_c6.jpg

225 ms

florerialilly_r3_c7.jpg

florerialilly_r3_c7.jpg

224 ms

florerialilly_r3_c8.jpg

florerialilly_r3_c8.jpg

222 ms

florerialilly_r3_c9.jpg

florerialilly_r3_c9.jpg

224 ms

florerialilly_r3_c10.jpg

florerialilly_r3_c10.jpg

277 ms

florerialilly_r3_c11.jpg

florerialilly_r3_c11.jpg

279 ms

florerialilly_r4_c2.jpg

florerialilly_r4_c2.jpg

282 ms

florerialilly_r4_c4.jpg

florerialilly_r4_c4.jpg

280 ms

florerialilly_r4_c6.jpg

florerialilly_r4_c6.jpg

278 ms

florerialilly_r4_c8.jpg

florerialilly_r4_c8.jpg

278 ms

florerialilly_r4_c10.jpg

florerialilly_r4_c10.jpg

337 ms

florerialilly_r4_c12.jpg

florerialilly_r4_c12.jpg

337 ms

img_vineta01.jpg

img_vineta01.jpg

338 ms

flag_spa_spa.jpg

flag_spa_spa.jpg

339 ms

flag_eng_spa.jpg

flag_eng_spa.jpg

339 ms

img_menu_izq_free.gif

img_menu_izq_free.gif

341 ms

bg_menu_izq_sup.gif

bg_menu_izq_sup.gif

398 ms

bg_menu_izq_left.gif

bg_menu_izq_left.gif

399 ms

img_menu_izq_categoria.gif

img_menu_izq_categoria.gif

401 ms

regalo_32f47_af0e6.jpg

regalo_32f47_af0e6.jpg

400 ms

img_menu_izq_pregunta_spa.gif

img_menu_izq_pregunta_spa.gif

401 ms

img_menu_izq_suscripcion_spa.gif

img_menu_izq_suscripcion_spa.gif

402 ms

img_menu_izq_siguenos_spa.gif

img_menu_izq_siguenos_spa.gif

460 ms

img_twitter_logo.gif

img_twitter_logo.gif

459 ms

img_facebook_logo.gif

img_facebook_logo.gif

460 ms

bg_menu_izq_right.gif

bg_menu_izq_right.gif

457 ms

__utm.gif

__utm.gif

38 ms

anchor

anchor

28 ms

bg_menu_izq_fondo_footer.jpg

bg_menu_izq_fondo_footer.jpg

371 ms

mail.jpg

mail.jpg

370 ms

styles__ltr.css

styles__ltr.css

29 ms

fox_d4a2c.php

fox_d4a2c.php

1501 ms

btn_comprar1_spa.gif

btn_comprar1_spa.gif

393 ms

btn_tell_to_friend_spa.jpg

btn_tell_to_friend_spa.jpg

390 ms

img_categoria_adicionales.gif

img_categoria_adicionales.gif

389 ms

bg_sep_v.gif

bg_sep_v.gif

392 ms

XIeAEBTR99FHtnz9GJvmJ1XccQZVVixQNk9jb_OO4Io.js

XIeAEBTR99FHtnz9GJvmJ1XccQZVVixQNk9jb_OO4Io.js

17 ms

webworker.js

webworker.js

40 ms

Caja%20x%2012%20rosas%20-%20p_f24a9.jpg

Caja%20x%2012%20rosas%20-%20p_f24a9.jpg

349 ms

logo_48.png

logo_48.png

15 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

45 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

48 ms

img_categoria_nacimientos.gif

img_categoria_nacimientos.gif

373 ms

img_categoria_arreglos_florales.gif

img_categoria_arreglos_florales.gif

370 ms

bg_sep_h.gif

bg_sep_h.gif

370 ms

img_categoria_defuncion.gif

img_categoria_defuncion.gif

370 ms

img_categoria_eventos.gif

img_categoria_eventos.gif

370 ms

img_categoria_osos_joyas.gif

img_categoria_osos_joyas.gif

427 ms

recaptcha__en.js

recaptcha__en.js

34 ms

img_categoria_cajas_ramos.gif

img_categoria_cajas_ramos.gif

379 ms

pc-a006.gif

pc-a006.gif

378 ms

to-r001.gif

to-r001.gif

378 ms

img_logo2.gif

img_logo2.gif

378 ms

img_tarjetas.gif

img_tarjetas.gif

435 ms

florerialilly_r3_c13.jpg

florerialilly_r3_c13.jpg

297 ms

florerialilly_r2_c15.jpg

florerialilly_r2_c15.jpg

267 ms

florerialilly_r3_c12.jpg

florerialilly_r3_c12.jpg

277 ms

florerialilly_r2_c14.jpg

florerialilly_r2_c14.jpg

256 ms

Accessibility Review

florerialilly.com accessibility score

62

Accessibility Issues

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.

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

florerialilly.com best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

florerialilly.com SEO score

58

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

Language and Encoding

  • Language Detected

    ES

  • 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 Florerialilly.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish 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 Florerialilly.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

florerialilly.com

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