Tools & Wizards About Us
planteriagroup.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

planteriagroup.com

Plants for Business | Corporate Office Plants | Planteria Group

Page Load Speed

4.8 sec in total

First Response

424 ms

Resources Loaded

3.5 sec

Page Rendered

837 ms

planteriagroup.com screenshot

About Website

Click here to check amazing Planteria Group content. Otherwise, check out these important facts you probably never knew about planteriagroup.com

Planteria Group are specialist interior landscape designers & plant suppliers for corporate spaces such as offices and businesses. Browse our selction now.

Visit planteriagroup.com

Key Findings

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

Performance Metrics

planteriagroup.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

www.planteriagroup.com

424 ms

critical.css

80 ms

jquery.min.js

160 ms

main.css

234 ms

cookieblocker.min.css

232 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 91% of them (79 requests) were addressed to the original Planteriagroup.com, 7% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (862 ms) belongs to the original domain Planteriagroup.com.

Page Optimization Overview & Recommendations

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

Content Size

2.8 MB

After Optimization

2.7 MB

  • HTML
  • Images

In fact, the total size of Planteriagroup.com main page is 2.8 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. 65% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 147.0 kB

  • Original 180.7 kB
  • After minification 176.1 kB
  • After compression 33.7 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 147.0 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.6 MB
  • After minification 2.6 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. Planteria Group images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 62 (85%)

Requests Now

73

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.planteriagroup.com

www.planteriagroup.com

424 ms

critical.css

critical.css

80 ms

jquery.min.js

jquery.min.js

160 ms

main.css

main.css

234 ms

cookieblocker.min.css

cookieblocker.min.css

232 ms

style.min.css

style.min.css

318 ms

style.basic.css

style.basic.css

242 ms

style-simple-red.css

style-simple-red.css

243 ms

elementor-icons.min.css

elementor-icons.min.css

239 ms

frontend.min.css

frontend.min.css

315 ms

swiper.min.css

swiper.min.css

323 ms

e-swiper.min.css

e-swiper.min.css

323 ms

post-14943.css

post-14943.css

327 ms

popup.min.css

popup.min.css

326 ms

uael-frontend.min.css

uael-frontend.min.css

555 ms

widget-social-icons.min.css

widget-social-icons.min.css

406 ms

brands.css

brands.css

405 ms

fontawesome.css

fontawesome.css

413 ms

solid.css

solid.css

416 ms

all.min.css

all.min.css

492 ms

v4-shims.min.css

v4-shims.min.css

485 ms

post-23704.css

post-23704.css

488 ms

style.min.css

style.min.css

491 ms

font-awesome.min.css

font-awesome.min.css

495 ms

jquery.min.js

jquery.min.js

641 ms

jquery-migrate.min.js

jquery-migrate.min.js

593 ms

v4-shims.min.js

v4-shims.min.js

592 ms

purify.min.js

purify.min.js

594 ms

scripts.js

scripts.js

592 ms

widget-spacer.min.css

widget-spacer.min.css

630 ms

widget-slides.min.css

widget-slides.min.css

755 ms

widget-heading.min.css

widget-heading.min.css

757 ms

widget-text-editor.min.css

widget-text-editor.min.css

757 ms

widget-call-to-action.min.css

widget-call-to-action.min.css

758 ms

transitions.min.css

transitions.min.css

758 ms

widget-image.min.css

widget-image.min.css

759 ms

frontend.min.js

frontend.min.js

759 ms

gtm4wp-contact-form-7-tracker.js

gtm4wp-contact-form-7-tracker.js

687 ms

css

css

31 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

592 ms

css2

css2

17 ms

navigation.js

navigation.js

535 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

564 ms

asl-prereq.js

asl-prereq.js

602 ms

asl-core.js

asl-core.js

642 ms

asl-results-vertical.js

asl-results-vertical.js

641 ms

asl-autocomplete.js

asl-autocomplete.js

568 ms

asl-load.js

asl-load.js

563 ms

asl-wrapper.js

asl-wrapper.js

563 ms

wp-polyfill.min.js

wp-polyfill.min.js

561 ms

index.js

index.js

639 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

641 ms

happy-addons.min.js

happy-addons.min.js

563 ms

imagesloaded.min.js

imagesloaded.min.js

559 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

553 ms

webpack.runtime.min.js

webpack.runtime.min.js

557 ms

frontend-modules.min.js

frontend-modules.min.js

558 ms

core.min.js

core.min.js

558 ms

frontend.min.js

frontend.min.js

562 ms

extension-equal-height.min.js

extension-equal-height.min.js

559 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

560 ms

hooks.min.js

hooks.min.js

463 ms

i18n.min.js

i18n.min.js

531 ms

frontend.min.js

frontend.min.js

570 ms

elements-handlers.min.js

elements-handlers.min.js

570 ms

Experian-14.jpg

Experian-14.jpg

767 ms

Endava-2.jpg

Endava-2.jpg

753 ms

GreenWallAlley-1.jpg

GreenWallAlley-1.jpg

692 ms

Planteria-39.jpg

Planteria-39.jpg

670 ms

Planteria-15.jpg

Planteria-15.jpg

757 ms

Planteria-38.jpg

Planteria-38.jpg

536 ms

Experian-10.jpg.webp

Experian-10.jpg.webp

688 ms

Experian-16.jpg

Experian-16.jpg

862 ms

OpenSans-Regular.ttf

OpenSans-Regular.ttf

798 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

30 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

91 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

121 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

120 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

120 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

121 ms

eicons.woff

eicons.woff

815 ms

OpenSans-Light.ttf

OpenSans-Light.ttf

814 ms

fa-brands-400.woff

fa-brands-400.woff

815 ms

fa-solid-900.woff

fa-solid-900.woff

841 ms

fa-regular-400.woff

fa-regular-400.woff

844 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

801 ms

cropped-logo.png.webp

cropped-logo.png.webp

515 ms

Accessibility Review

planteriagroup.com accessibility score

96

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.

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

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

planteriagroup.com SEO score

93

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

Links do not have descriptive text

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

planteriagroup.com

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