Report Summary

  • 87

    Performance

    Renders faster than
    90% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

plantglo.com

Shared Pet Sitting - dogs, cats

Page Load Speed

1.6 sec in total

First Response

523 ms

Resources Loaded

962 ms

Page Rendered

120 ms

plantglo.com screenshot

About Website

Welcome to plantglo.com homepage info - get ready to check Plantglo best content right away, or after learning these important things about plantglo.com

Visit plantglo.com

Key Findings

We analyzed Plantglo.com page load time and found that the first response time was 523 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

plantglo.com performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

87/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.29

41/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

access.php

523 ms

customhome.css

67 ms

custom.css

62 ms

jquery.min.js

74 ms

index.js

63 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 86% of them (6 requests) were addressed to the original Plantglo.com, 14% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (523 ms) belongs to the original domain Plantglo.com.

Page Optimization Overview & Recommendations

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

Content Size

244.5 kB

After Optimization

231.4 kB

In fact, the total size of Plantglo.com main page is 244.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 203.2 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 858 B

  • Original 1.5 kB
  • After minification 1.4 kB
  • After compression 624 B

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 858 B or 58% of the original size.

Image Optimization

-2%

Potential reduce by 4.3 kB

  • Original 203.2 kB
  • After minification 198.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. Plantglo images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 695 B

  • Original 30.6 kB
  • After minification 30.1 kB
  • After compression 29.9 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

-78%

Potential reduce by 7.2 kB

  • Original 9.3 kB
  • After minification 6.5 kB
  • After compression 2.0 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. Plantglo.com needs all CSS files to be minified and compressed as it can save up to 7.2 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plantglo. According to our analytics all requests are already optimized.

Accessibility Review

plantglo.com accessibility score

93

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.

Best Practices

plantglo.com best practices score

58

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

High

Browser errors were logged to the console

SEO Factors

plantglo.com SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plantglo.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Plantglo.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 Plantglo. 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: