Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

commons.hortipedia.com

Hortipedia - commons

Page Load Speed

15 sec in total

First Response

599 ms

Resources Loaded

14.3 sec

Page Rendered

139 ms

commons.hortipedia.com screenshot

About Website

Welcome to commons.hortipedia.com homepage info - get ready to check Commons Hortipedia best content for Russia right away, or after learning these important things about commons.hortipedia.com

Hortipedia commons is the media repository of the GardenInfoPortal hortipedia.com and contains all the images used in the various plant articles. The database includes pictures of plants sorted by nam...

Visit commons.hortipedia.com

Key Findings

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

Performance Metrics

commons.hortipedia.com performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

74/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.152

75/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

Main_Page

599 ms

load.php

499 ms

load.php

790 ms

load.php

1038 ms

load.php

2479 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 35% of them (21 requests) were addressed to the original Commons.hortipedia.com, 12% (7 requests) were made to Apis.google.com and 8% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (7.3 sec) relates to the external source Freegeoip.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 454.3 kB (70%)

Content Size

651.8 kB

After Optimization

197.5 kB

In fact, the total size of Commons.hortipedia.com main page is 651.8 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. 45% of websites need less resources to load. HTML takes 349.9 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 308.3 kB

  • Original 349.9 kB
  • After minification 347.4 kB
  • After compression 41.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 308.3 kB or 88% of the original size.

Image Optimization

-3%

Potential reduce by 2.2 kB

  • Original 78.4 kB
  • After minification 76.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. Commons Hortipedia images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 143.8 kB

  • Original 223.5 kB
  • After minification 223.4 kB
  • After compression 79.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 143.8 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (65%)

Requests Now

57

After Optimization

20

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

Accessibility Review

commons.hortipedia.com accessibility score

75

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

commons.hortipedia.com best practices score

83

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

Serves images with low resolution

SEO Factors

commons.hortipedia.com SEO score

83

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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