Tools & Wizards About Us
marriedtoplants.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 70

    SEO

    Google-friendlier than
    29% of websites

marriedtoplants.com

Married To Plants

Page Load Speed

2.8 sec in total

First Response

409 ms

Resources Loaded

1.7 sec

Page Rendered

715 ms

marriedtoplants.com screenshot

About Website

Click here to check amazing Married To Plants content for United States. Otherwise, check out these important facts you probably never knew about marriedtoplants.com

Visit marriedtoplants.com

Key Findings

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

Performance Metrics

marriedtoplants.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value28.0 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value1.456

0/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

www.marriedtoplants.com

409 ms

wpp.js

124 ms

style.css

129 ms

style.min.css

184 ms

styles.css

127 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 73% of them (57 requests) were addressed to the original Marriedtoplants.com, 13% (10 requests) were made to Fonts.gstatic.com and 9% (7 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (622 ms) belongs to the original domain Marriedtoplants.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 281.9 kB (2%)

Content Size

13.8 MB

After Optimization

13.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Marriedtoplants.com main page is 13.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 13.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 59.8 kB

  • Original 75.0 kB
  • After minification 74.5 kB
  • After compression 15.2 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 59.8 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 86.7 kB

  • Original 13.3 MB
  • After minification 13.3 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. Married To Plants images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 131.2 kB

  • Original 325.0 kB
  • After minification 325.0 kB
  • After compression 193.8 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 131.2 kB or 40% of the original size.

CSS Optimization

-13%

Potential reduce by 4.2 kB

  • Original 33.0 kB
  • After minification 32.7 kB
  • After compression 28.8 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. Marriedtoplants.com needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (45%)

Requests Now

67

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.marriedtoplants.com

www.marriedtoplants.com

409 ms

wpp.js

wpp.js

124 ms

style.css

style.css

129 ms

style.min.css

style.min.css

184 ms

styles.css

styles.css

127 ms

wpp.css

wpp.css

128 ms

lightbox.min.css

lightbox.min.css

125 ms

css

css

22 ms

jquery.min.js

jquery.min.js

253 ms

jquery-migrate.min.js

jquery-migrate.min.js

192 ms

responsive-menu.js

responsive-menu.js

190 ms

css

css

36 ms

css

css

41 ms

css

css

40 ms

css

css

40 ms

css

css

38 ms

uniform.default.css

uniform.default.css

191 ms

jquery.uniform.js

jquery.uniform.js

191 ms

adsbygoogle.js

adsbygoogle.js

32 ms

soliloquy.css

soliloquy.css

244 ms

style.css

style.css

350 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

351 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

351 ms

wp-polyfill.min.js

wp-polyfill.min.js

359 ms

hooks.min.js

hooks.min.js

359 ms

i18n.min.js

i18n.min.js

357 ms

index.js

index.js

357 ms

index.js

index.js

357 ms

wp-lightbox-2.min.js

wp-lightbox-2.min.js

357 ms

soliloquy-min.js

soliloquy-min.js

518 ms

analytics.js

analytics.js

88 ms

logo.jpg

logo.jpg

229 ms

search-btn.png

search-btn.png

230 ms

dictyocaryum-lamarckianum-the-lost-city-colombia-1399x460_c.jpg

dictyocaryum-lamarckianum-the-lost-city-colombia-1399x460_c.jpg

435 ms

holder.gif

holder.gif

230 ms

left-arrow.jpg

left-arrow.jpg

231 ms

right-arrow.jpg

right-arrow.jpg

232 ms

dictyocaryum-lamarckianum-the-lost-city-colombia.jpg

dictyocaryum-lamarckianum-the-lost-city-colombia.jpg

500 ms

Leaf.jpg

Leaf.jpg

230 ms

croton-propagation-cut-stem.jpg

croton-propagation-cut-stem.jpg

560 ms

geiger-garden-agave-pots-carcharodons.jpg

geiger-garden-agave-pots-carcharodons.jpg

553 ms

cordia-lutea-flowers-close.jpg

cordia-lutea-flowers-close.jpg

558 ms

planter-bed-preparation-rototiller-close.jpg

planter-bed-preparation-rototiller-close.jpg

567 ms

dry-creek-bed-medium-river-rock-placement-2.jpg

dry-creek-bed-medium-river-rock-placement-2.jpg

563 ms

garden-project-update-moving-sprinklers.jpg

garden-project-update-moving-sprinklers.jpg

568 ms

licuala-ramsayi-transplant-finished.jpg

licuala-ramsayi-transplant-finished.jpg

620 ms

next-btn.png

next-btn.png

619 ms

bio_photo.jpg

bio_photo.jpg

622 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xo.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xo.woff

152 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xo.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xo.woff

154 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

154 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

155 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

155 ms

KFOlCnqEu92Fr1MmYUtfBBc-.woff

KFOlCnqEu92Fr1MmYUtfBBc-.woff

155 ms

wlp_gwjKBV1pqhv43Ic.woff

wlp_gwjKBV1pqhv43Ic.woff

164 ms

wlpygwjKBV1pqhND-ZQW-WU.woff

wlpygwjKBV1pqhND-ZQW-WU.woff

167 ms

TUZyzwprpvBS1izr_vOECuSZ.woff

TUZyzwprpvBS1izr_vOECuSZ.woff

165 ms

TUZ3zwprpvBS1izr_vOMscGKfrUE.woff

TUZ3zwprpvBS1izr_vOMscGKfrUE.woff

164 ms

css

css

136 ms

collect

collect

53 ms

footer-bg.jpg

footer-bg.jpg

412 ms

divider.jpg

divider.jpg

414 ms

subscribe-btn.png

subscribe-btn.png

420 ms

fb-sprite.png

fb-sprite.png

469 ms

pin-sprite.png

pin-sprite.png

473 ms

instagram-v1.png

instagram-v1.png

472 ms

preloader.gif

preloader.gif

474 ms

slider-arrows-horizontal.png

slider-arrows-horizontal.png

468 ms

slider-arrows-vertical.png

slider-arrows-vertical.png

479 ms

pause-play.png

pause-play.png

525 ms

js

js

91 ms

croton-propagation-cut-stem-1399x460_c.jpg

croton-propagation-cut-stem-1399x460_c.jpg

477 ms

geiger-garden-agave-pots-carcharodons-1399x460_c.jpg

geiger-garden-agave-pots-carcharodons-1399x460_c.jpg

421 ms

cordia-lutea-flowers-close-1399x460_c.jpg

cordia-lutea-flowers-close-1399x460_c.jpg

420 ms

planter-bed-preparation-rototiller-close-1399x460_c.jpg

planter-bed-preparation-rototiller-close-1399x460_c.jpg

426 ms

left_arrows.png

left_arrows.png

433 ms

right_arrows.png

right_arrows.png

480 ms

select-btn.jpg

select-btn.jpg

484 ms

Accessibility Review

marriedtoplants.com accessibility score

85

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

marriedtoplants.com SEO score

70

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

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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

marriedtoplants.com

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