Tools & Wizards About Us
florpedia.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

florpedia.com

Flores, plantas, rosas y ramos de flores en Florpedia.com

Page Load Speed

3.6 sec in total

First Response

343 ms

Resources Loaded

2.8 sec

Page Rendered

462 ms

florpedia.com screenshot

About Website

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

Florpedia: portal sobre flores, plantas y jardín con consejos para el cuidado de rosas, ramos de flores, orquídeas, bonsáis, césped...

Visit florpedia.com

Key Findings

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

Performance Metrics

florpedia.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.387

27/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

florpedia.com

343 ms

www.florpedia.com

1443 ms

wp-emoji-release.min.js

87 ms

styles.css

168 ms

jquery.js

314 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 69% of them (31 requests) were addressed to the original Florpedia.com, 9% (4 requests) were made to Platform.twitter.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Florpedia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.5 kB (3%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Florpedia.com 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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 36.2 kB

  • Original 45.7 kB
  • After minification 43.3 kB
  • After compression 9.5 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 36.2 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 198 B

  • Original 1.1 MB
  • After minification 1.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. Florpedia images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 961 B

  • Original 148.6 kB
  • After minification 148.6 kB
  • After compression 147.6 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

-11%

Potential reduce by 168 B

  • Original 1.5 kB
  • After minification 1.5 kB
  • After compression 1.3 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. Florpedia.com needs all CSS files to be minified and compressed as it can save up to 168 B or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (47%)

Requests Now

43

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

florpedia.com

florpedia.com

343 ms

www.florpedia.com

www.florpedia.com

1443 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

87 ms

styles.css

styles.css

168 ms

jquery.js

jquery.js

314 ms

jquery-migrate.min.js

jquery-migrate.min.js

241 ms

estiloflorpedia.css

estiloflorpedia.css

242 ms

comment-reply.min.js

comment-reply.min.js

241 ms

scripts.js

scripts.js

242 ms

wp-embed.min.js

wp-embed.min.js

249 ms

analytics.js

analytics.js

40 ms

coloresbarraizquierdayderec.gif

coloresbarraizquierdayderec.gif

101 ms

details_nav_arrow.gif

details_nav_arrow.gif

98 ms

palo-menu-grande.gif

palo-menu-grande.gif

99 ms

%C3%81rboles-y-arbustos.jpg

%C3%81rboles-y-arbustos.jpg

164 ms

Bons%C3%A1is.jpg

Bons%C3%A1is.jpg

284 ms

C%C3%A9sped.jpg

C%C3%A9sped.jpg

284 ms

Claveles.jpg

Claveles.jpg

321 ms

Flores.jpg

Flores.jpg

322 ms

Jard%C3%ADn.jpg

Jard%C3%ADn.jpg

326 ms

Orqu%C3%ADdeas.jpg

Orqu%C3%ADdeas.jpg

281 ms

Plantas.jpg

Plantas.jpg

395 ms

Plantas-de-interior.jpg

Plantas-de-interior.jpg

321 ms

Plantas-ex%C3%B3ticas.jpg

Plantas-ex%C3%B3ticas.jpg

323 ms

Plantas-medicinales.jpg

Plantas-medicinales.jpg

481 ms

Plantas-suculentas.jpg

Plantas-suculentas.jpg

402 ms

Ramos-de-flores.jpg

Ramos-de-flores.jpg

481 ms

Rosas.jpg

Rosas.jpg

411 ms

pixelbarrainferior1.gif

pixelbarrainferior1.gif

412 ms

pixelbarrainferior2.gif

pixelbarrainferior2.gif

471 ms

florpedia-header.png

florpedia-header.png

635 ms

pixelbarrasuperior.gif

pixelbarrasuperior.gif

479 ms

widgets.js

widgets.js

145 ms

all.js

all.js

33 ms

plusone.js

plusone.js

68 ms

collect

collect

36 ms

all.js

all.js

5 ms

71 ms

js

js

98 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

95 ms

settings

settings

98 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

31 ms

embeds

embeds

43 ms

follow_button.2f70fb173b9000da126c79afe2098f02.es.html

follow_button.2f70fb173b9000da126c79afe2098f02.es.html

42 ms

Accessibility Review

florpedia.com accessibility score

70

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

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

Best Practices

florpedia.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

florpedia.com SEO score

71

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

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

florpedia.com

Open Graph data is detected on the main page of Florpedia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: