Tools & Wizards About Us
florikebana.es screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

florikebana.es

Floristeria Ikebana. Arte floral en Logroño. Floristerias Logroño

Page Load Speed

2.3 sec in total

First Response

423 ms

Resources Loaded

1.6 sec

Page Rendered

205 ms

florikebana.es screenshot

About Website

Welcome to florikebana.es homepage info - get ready to check Flor Ikebana best content right away, or after learning these important things about florikebana.es

Floristeria en Logroño. Arte floral. Floristerias Logroño. Ramos de novia, centros y cestas de flores, plantas, coronas; decoracion de restaurantes, iglesias, convenciones, eventos

Visit florikebana.es

Key Findings

We analyzed Florikebana.es page load time and found that the first response time was 423 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

florikebana.es performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

florikebana.es

423 ms

ikebana.js

226 ms

default.css

225 ms

slide-ofertas.css

531 ms

jquery.min.js

10 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 89% of them (33 requests) were addressed to the original Florikebana.es, 5% (2 requests) were made to Ajax.googleapis.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (777 ms) belongs to the original domain Florikebana.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 31.0 kB (5%)

Content Size

602.7 kB

After Optimization

571.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Florikebana.es main page is 602.7 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. 40% of websites need less resources to load. Images take 497.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 12.9 kB

  • Original 15.7 kB
  • After minification 13.9 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 1.8 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 12.9 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 8.3 kB

  • Original 497.2 kB
  • After minification 488.9 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. Flor Ikebana images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 895 B

  • Original 79.3 kB
  • After minification 79.3 kB
  • After compression 78.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. This website has mostly compressed JavaScripts.

CSS Optimization

-84%

Potential reduce by 8.9 kB

  • Original 10.6 kB
  • After minification 7.4 kB
  • After compression 1.7 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. Florikebana.es needs all CSS files to be minified and compressed as it can save up to 8.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (11%)

Requests Now

35

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

florikebana.es

florikebana.es

423 ms

ikebana.js

ikebana.js

226 ms

default.css

default.css

225 ms

slide-ofertas.css

slide-ofertas.css

531 ms

jquery.min.js

jquery.min.js

10 ms

jquery-ui.min.js

jquery-ui.min.js

16 ms

jqueryTooltip.js

jqueryTooltip.js

543 ms

jquery.wslide.js

jquery.wslide.js

544 ms

fondo.jpg

fondo.jpg

117 ms

fondoquetecagas.jpg

fondoquetecagas.jpg

213 ms

img02.gif

img02.gif

116 ms

especial-empresas.png

especial-empresas.png

394 ms

665_g.JPG

665_g.JPG

491 ms

616_g.JPG

616_g.JPG

493 ms

661_g.JPG

661_g.JPG

497 ms

496_g.JPG

496_g.JPG

524 ms

788_g.JPG

788_g.JPG

523 ms

12_g.JPG

12_g.JPG

490 ms

506_g.JPG

506_g.JPG

586 ms

731_g.JPG

731_g.JPG

587 ms

618_g.JPG

618_g.JPG

589 ms

551_g.JPG

551_g.JPG

592 ms

844_g.JPG

844_g.JPG

625 ms

596_g.GIF

596_g.GIF

626 ms

818_g.PNG

818_g.PNG

682 ms

729_g.JPG

729_g.JPG

683 ms

610_g.JPG

610_g.JPG

685 ms

689_g.JPG

689_g.JPG

687 ms

802_g.JPG

802_g.JPG

727 ms

783_g.JPG

783_g.JPG

727 ms

webtienda.png

webtienda.png

777 ms

lateral1.jpg

lateral1.jpg

777 ms

img03oca.gif

img03oca.gif

209 ms

img03.gif

img03.gif

209 ms

img16.gif

img16.gif

203 ms

ga.js

ga.js

8 ms

__utm.gif

__utm.gif

12 ms

Accessibility Review

florikebana.es 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

florikebana.es best practices score

50

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

SEO Factors

florikebana.es SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

florikebana.es

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