Tools & Wizards About Us
plantable.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

plantable.com

Plantable | Plant-based meals, health coaching, and support

Page Load Speed

2.9 sec in total

First Response

411 ms

Resources Loaded

1.4 sec

Page Rendered

1.1 sec

plantable.com screenshot

About Website

Click here to check amazing Plantable content for United States. Otherwise, check out these important facts you probably never knew about plantable.com

Plantable makes it easy to lose weight and address chronic disease with plant‑based, no added sugar, chef‑crafted meals delivered to your door, and a coach to help guide the way. Visit us now!

Visit plantable.com

Key Findings

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

Performance Metrics

plantable.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value33.6 s

0/100

10%

Network Requests Diagram

www.plantable.com

411 ms

jquery-1.11.2.js

32 ms

Load_Screen_Style.min.css

53 ms

main.css

71 ms

module_74384472955_Top-Message-Banner.min.css

65 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 53% of them (28 requests) were addressed to the original Plantable.com, 17% (9 requests) were made to Fonts.gstatic.com and 8% (4 requests) were made to No-cache.hubspot.com. The less responsive or slowest element that took the longest time to load (654 ms) belongs to the original domain Plantable.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (20%)

Content Size

7.3 MB

After Optimization

5.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 74.3 kB

  • Original 93.1 kB
  • After minification 77.5 kB
  • After compression 18.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. This page needs HTML code to be minified as it can gain 15.6 kB, which is 17% 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 74.3 kB or 80% of the original size.

Image Optimization

-20%

Potential reduce by 1.4 MB

  • Original 7.0 MB
  • After minification 5.7 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. Obviously, Plantable needs image optimization as it can save up to 1.4 MB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-5%

Potential reduce by 7.1 kB

  • Original 140.0 kB
  • After minification 140.0 kB
  • After compression 132.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

-36%

Potential reduce by 21.7 kB

  • Original 60.6 kB
  • After minification 60.6 kB
  • After compression 38.9 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. Plantable.com needs all CSS files to be minified and compressed as it can save up to 21.7 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (59%)

Requests Now

39

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.plantable.com

www.plantable.com

411 ms

jquery-1.11.2.js

jquery-1.11.2.js

32 ms

Load_Screen_Style.min.css

Load_Screen_Style.min.css

53 ms

main.css

main.css

71 ms

module_74384472955_Top-Message-Banner.min.css

module_74384472955_Top-Message-Banner.min.css

65 ms

v2.js

v2.js

84 ms

index.js

index.js

46 ms

embed.js

embed.js

46 ms

main.min.js

main.min.js

67 ms

project.js

project.js

87 ms

module_68139222092_Header.min.js

module_68139222092_Header.min.js

87 ms

project.js

project.js

87 ms

v2.js

v2.js

169 ms

20425213.js

20425213.js

271 ms

index.js

index.js

105 ms

font-awesome.min.css

font-awesome.min.css

49 ms

css2

css2

45 ms

fbevents.js

fbevents.js

165 ms

1c8cd9e1-e277-4553-b7b8-dc248603d131.png

1c8cd9e1-e277-4553-b7b8-dc248603d131.png

297 ms

0ac34a95-e5d0-4458-a86f-97b211996bd3.png

0ac34a95-e5d0-4458-a86f-97b211996bd3.png

355 ms

ff76c8a3-007e-4a72-a01a-f0056b63b7bc.png

ff76c8a3-007e-4a72-a01a-f0056b63b7bc.png

409 ms

86d4204e-d842-4bd2-8a41-d84b3d0e618d.png

86d4204e-d842-4bd2-8a41-d84b3d0e618d.png

419 ms

Group.png

Group.png

162 ms

Cancel.png

Cancel.png

172 ms

Pop-Up.webp

Pop-Up.webp

402 ms

LazyLoadImg.webp

LazyLoadImg.webp

173 ms

Screen%20Shot%202022-09-07%20at%201.33.24%20PM.png

Screen%20Shot%202022-09-07%20at%201.33.24%20PM.png

389 ms

Screen%20Shot%202022-09-07%20at%201.38.30%20PM.png

Screen%20Shot%202022-09-07%20at%201.38.30%20PM.png

654 ms

Screen%20Shot%202022-09-07%20at%201.36.45%20PM.png

Screen%20Shot%202022-09-07%20at%201.36.45%20PM.png

394 ms

Pick%20a%20ship%20date%20(1).png

Pick%20a%20ship%20date%20(1).png

273 ms

Choose%20meals%20(1).png

Choose%20meals%20(1).png

418 ms

Build%20a%20plan%20(1).png

Build%20a%20plan%20(1).png

353 ms

Delivered%20to%20your%20door%20(1).png

Delivered%20to%20your%20door%20(1).png

414 ms

www.plantable.com

www.plantable.com

572 ms

image%20161.png

image%20161.png

416 ms

Screenshot_2.webp

Screenshot_2.webp

443 ms

LazyLoadImg.webp

LazyLoadImg.webp

444 ms

FoundersGroteskTextWeb-Light.woff

FoundersGroteskTextWeb-Light.woff

166 ms

FoundersGroteskTextWeb-Bold.woff

FoundersGroteskTextWeb-Bold.woff

236 ms

NoeDisplayBold.woff

NoeDisplayBold.woff

298 ms

FoundersGroteskMonoWeb-Regular.woff

FoundersGroteskMonoWeb-Regular.woff

298 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

92 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

117 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

201 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

165 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

198 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

198 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

196 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

197 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

199 ms

20425213.js

20425213.js

192 ms

banner.js

banner.js

160 ms

collectedforms.js

collectedforms.js

123 ms

Accessibility Review

plantable.com accessibility score

95

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

High

Page has valid source maps

SEO Factors

plantable.com SEO score

86

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

plantable.com

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