Tools & Wizards About Us
planningpretty.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

planningpretty.com

Planning Pretty - Planning Pretty

Page Load Speed

9.4 sec in total

First Response

168 ms

Resources Loaded

7.7 sec

Page Rendered

1.6 sec

planningpretty.com screenshot

About Website

Visit planningpretty.com now to see the best up-to-date Planning Pretty content for United States and also check out these interesting facts you probably never knew about planningpretty.com

Planning Pretty is a home decor brand that shares tips for decorating homes, offers design services and an online for the latest decor trends

Visit planningpretty.com

Key Findings

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

Performance Metrics

planningpretty.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.623

10/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

planningpretty.com

168 ms

www.planningpretty.com

1223 ms

js

91 ms

all.min.css

147 ms

style-blocks.build.css

210 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 55% of them (48 requests) were addressed to the original Planningpretty.com, 18% (16 requests) were made to I0.wp.com and 13% (11 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Planningpretty.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 400.5 kB (6%)

Content Size

6.4 MB

After Optimization

6.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Planningpretty.com main page is 6.4 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 5.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 107.9 kB

  • Original 131.0 kB
  • After minification 130.1 kB
  • After compression 23.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 107.9 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 113.3 kB

  • Original 5.8 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. Planning Pretty images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 135.7 kB

  • Original 315.3 kB
  • After minification 310.8 kB
  • After compression 179.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 135.7 kB or 43% of the original size.

CSS Optimization

-26%

Potential reduce by 43.6 kB

  • Original 167.7 kB
  • After minification 144.7 kB
  • After compression 124.1 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. Planningpretty.com needs all CSS files to be minified and compressed as it can save up to 43.6 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (72%)

Requests Now

78

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Planning Pretty. 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 25 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

planningpretty.com

planningpretty.com

168 ms

www.planningpretty.com

www.planningpretty.com

1223 ms

js

js

91 ms

all.min.css

all.min.css

147 ms

style-blocks.build.css

style-blocks.build.css

210 ms

sbi-styles.min.css

sbi-styles.min.css

262 ms

style.css

style.css

206 ms

style.min.css

style.min.css

32 ms

blocks.style.build.css

blocks.style.build.css

207 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

37 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

38 ms

styles.css

styles.css

408 ms

style.css

style.css

168 ms

frontend.min.css

frontend.min.css

283 ms

flatpickr.min.css

flatpickr.min.css

221 ms

select2.min.css

select2.min.css

222 ms

css2

css2

81 ms

dashicons.min.css

dashicons.min.css

13 ms

front-end.css

front-end.css

231 ms

style.css

style.css

274 ms

font-awesome.min.css

font-awesome.min.css

74 ms

jetpack.css

jetpack.css

9 ms

jquery.min.js

jquery.min.js

15 ms

jquery-migrate.min.js

jquery-migrate.min.js

18 ms

frontend-gtag.min.js

frontend-gtag.min.js

288 ms

jquery.nailthumb.1.0.min.js

jquery.nailthumb.1.0.min.js

300 ms

flatpickr.min.js

flatpickr.min.js

299 ms

select2.min.js

select2.min.js

350 ms

classic-10_7.css

classic-10_7.css

63 ms

mc-validate.js

mc-validate.js

86 ms

tooltipster.bundle.min.css

tooltipster.bundle.min.css

359 ms

tooltipster-borderless.min.css

tooltipster-borderless.min.css

354 ms

featherlight.min.css

featherlight.min.css

364 ms

font-awesome.min.css

font-awesome.min.css

70 ms

style-new.min.css

style-new.min.css

360 ms

submit.js

submit.js

541 ms

pagecount.min.js

pagecount.min.js

541 ms

hooks.min.js

hooks.min.js

30 ms

i18n.min.js

i18n.min.js

30 ms

index.js

index.js

542 ms

index.js

index.js

541 ms

frontend.min.js

frontend.min.js

542 ms

dismiss.js

dismiss.js

596 ms

dismiss.js

dismiss.js

596 ms

hoverIntent.min.js

hoverIntent.min.js

50 ms

superfish.min.js

superfish.min.js

596 ms

superfish.args.min.js

superfish.args.min.js

595 ms

skip-links.min.js

skip-links.min.js

595 ms

block-effects.js

block-effects.js

595 ms

responsive-menus.min.js

responsive-menus.min.js

630 ms

smooth-scroll.js

smooth-scroll.js

626 ms

top-banner.js

top-banner.js

627 ms

eu-cookie-law.min.js

eu-cookie-law.min.js

50 ms

e-202431.js

e-202431.js

56 ms

sbi-scripts.min.js

sbi-scripts.min.js

638 ms

tooltipster.bundle.min.js

tooltipster.bundle.min.js

639 ms

featherlight.min.js

featherlight.min.js

551 ms

jstz.min.js

jstz.min.js

564 ms

script.min.js

script.min.js

565 ms

targeting.min.js

targeting.min.js

565 ms

cropped-logo-transparent-landing.png

cropped-logo-transparent-landing.png

152 ms

Copy-of-Glamour-3-images.png

Copy-of-Glamour-3-images.png

177 ms

2a488d8e55898a38c161e2c591e175d193d05d29061dc54930669b6d4aeefe3d_1e05cb69-54b5-4e53-aee8-23e78a09c4dc-300x300.jpg

2a488d8e55898a38c161e2c591e175d193d05d29061dc54930669b6d4aeefe3d_1e05cb69-54b5-4e53-aee8-23e78a09c4dc-300x300.jpg

174 ms

palm_pillow.jpeg

palm_pillow.jpeg

207 ms

Pineapple_Shaker.jpg

Pineapple_Shaker.jpg

177 ms

dining-room-lounge-1.jpg

dining-room-lounge-1.jpg

1210 ms

woodland-nursery-reveal-19-683x1024.jpg

woodland-nursery-reveal-19-683x1024.jpg

187 ms

thanksgiving-tablescape-19-scaled-e1600839125856-675x1024.jpg

thanksgiving-tablescape-19-scaled-e1600839125856-675x1024.jpg

184 ms

apple-picking-03-1.jpg

apple-picking-03-1.jpg

414 ms

floral-playmat-07.jpg

floral-playmat-07.jpg

193 ms

IMG_5631.jpg

IMG_5631.jpg

206 ms

IMG_5610.jpg

IMG_5610.jpg

229 ms

domino.png

domino.png

746 ms

HGTV.png

HGTV.png

233 ms

apartment_therapy-1.jpeg

apartment_therapy-1.jpeg

234 ms

aphrochic-logo-glow-254-e1601947483245.png

aphrochic-logo-glow-254-e1601947483245.png

902 ms

sbi-sprite.png

sbi-sprite.png

320 ms

symbol-defs.svg

symbol-defs.svg

414 ms

Photo-Sep-27-1-47-28-PM.jpg

Photo-Sep-27-1-47-28-PM.jpg

173 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf

106 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZg.ttf

145 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf

170 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZg.ttf

172 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

230 ms

CaliforniaPalms_Script.otf

CaliforniaPalms_Script.otf

401 ms

royal-hawaiian.jpg

royal-hawaiian.jpg

541 ms

Photo-Sep-27-1-47-28-PM.jpg

Photo-Sep-27-1-47-28-PM.jpg

373 ms

wARDj0u

wARDj0u

11 ms

Accessibility Review

planningpretty.com accessibility score

96

Accessibility Issues

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

planningpretty.com best practices score

75

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

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

robots.txt is not valid

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

planningpretty.com

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