Tools & Wizards About Us
orchidnest.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

orchidnest.com

Home - Welcome to the Orchid Nest

Page Load Speed

3.7 sec in total

First Response

163 ms

Resources Loaded

3.1 sec

Page Rendered

387 ms

orchidnest.com screenshot

About Website

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

Welcome toThe Orchid Nest Are you pregnant and want to create YOUR best birth experience?Are you postpartum and feel overwhelmed with your new human? We Got You! Providing support in […]

Visit orchidnest.com

Key Findings

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

Performance Metrics

orchidnest.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value1,660 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.581

11/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

orchidnest.com

163 ms

orchidnest.com

1664 ms

style.min.css

128 ms

mediaelementplayer-legacy.min.css

182 ms

wp-mediaelement.min.css

183 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 82% of them (88 requests) were addressed to the original Orchidnest.com, 8% (9 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Orchidnest.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 287.6 kB (23%)

Content Size

1.2 MB

After Optimization

946.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Orchidnest.com main page is 1.2 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. 60% of websites need less resources to load. Javascripts take 602.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 86.6 kB

  • Original 110.1 kB
  • After minification 108.5 kB
  • After compression 23.5 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 86.6 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 188.1 kB
  • After minification 188.1 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. Orchid Nest images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 66.4 kB

  • Original 602.1 kB
  • After minification 601.6 kB
  • After compression 535.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 66.4 kB or 11% of the original size.

CSS Optimization

-40%

Potential reduce by 134.6 kB

  • Original 334.1 kB
  • After minification 334.1 kB
  • After compression 199.6 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. Orchidnest.com needs all CSS files to be minified and compressed as it can save up to 134.6 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 89 (94%)

Requests Now

95

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

orchidnest.com

orchidnest.com

163 ms

orchidnest.com

orchidnest.com

1664 ms

style.min.css

style.min.css

128 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

182 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

183 ms

style-index.css

style-index.css

185 ms

utilities.css

utilities.css

187 ms

woocommerce-layout.css

woocommerce-layout.css

190 ms

woocommerce.css

woocommerce.css

195 ms

tribe-events-single-skeleton.min.css

tribe-events-single-skeleton.min.css

247 ms

tribe-events-single-full.min.css

tribe-events-single-full.min.css

249 ms

widget-base.min.css

widget-base.min.css

257 ms

header-footer-elementor.css

header-footer-elementor.css

263 ms

elementor-icons.min.css

elementor-icons.min.css

260 ms

frontend-lite.min.css

frontend-lite.min.css

266 ms

swiper.min.css

swiper.min.css

311 ms

post-793.css

post-793.css

311 ms

frontend-lite.min.css

frontend-lite.min.css

324 ms

global.css

global.css

392 ms

post-3231.css

post-3231.css

326 ms

frontend.css

frontend.css

333 ms

wpforms-full.min.css

wpforms-full.min.css

431 ms

style.css

style.css

372 ms

style.min.css

style.min.css

390 ms

theme.min.css

theme.min.css

391 ms

header-footer.min.css

header-footer.min.css

397 ms

post-3206.css

post-3206.css

437 ms

post-3220.css

post-3220.css

452 ms

post-2395.css

post-2395.css

453 ms

ekiticons.css

ekiticons.css

459 ms

widget-styles.css

widget-styles.css

536 ms

responsive.css

responsive.css

499 ms

general.min.css

general.min.css

501 ms

css

css

30 ms

fontawesome.min.css

fontawesome.min.css

578 ms

solid.min.css

solid.min.css

515 ms

brands.min.css

brands.min.css

523 ms

utilities.js

utilities.js

563 ms

js

js

77 ms

api.js

api.js

80 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

514 ms

wc-blocks.css

wc-blocks.css

463 ms

photoswipe.min.css

photoswipe.min.css

413 ms

default-skin.min.css

default-skin.min.css

429 ms

choices.min.css

choices.min.css

451 ms

jquery.min.js

jquery.min.js

507 ms

jquery-migrate.min.js

jquery-migrate.min.js

457 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

451 ms

add-to-cart.min.js

add-to-cart.min.js

412 ms

js.cookie.min.js

js.cookie.min.js

428 ms

woocommerce.min.js

woocommerce.min.js

540 ms

sourcebuster.min.js

sourcebuster.min.js

537 ms

order-attribution.min.js

order-attribution.min.js

535 ms

hello-frontend.min.js

hello-frontend.min.js

533 ms

frontend-script.js

frontend-script.js

492 ms

widget-scripts.js

widget-scripts.js

557 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

478 ms

general.min.js

general.min.js

476 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

467 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

496 ms

webpack.runtime.min.js

webpack.runtime.min.js

478 ms

frontend-modules.min.js

frontend-modules.min.js

545 ms

hooks.min.js

hooks.min.js

472 ms

i18n.min.js

i18n.min.js

471 ms

frontend.min.js

frontend.min.js

507 ms

waypoints.min.js

waypoints.min.js

502 ms

core.min.js

core.min.js

486 ms

frontend.min.js

frontend.min.js

489 ms

elements-handlers.min.js

elements-handlers.min.js

479 ms

animate-circle.min.js

animate-circle.min.js

528 ms

elementor.js

elementor.js

509 ms

jquery.sticky.min.js

jquery.sticky.min.js

496 ms

underscore-before.js

underscore-before.js

491 ms

underscore.min.js

underscore.min.js

466 ms

underscore-after.js

underscore-after.js

458 ms

wp-util.min.js

wp-util.min.js

507 ms

frontend.min.js

frontend.min.js

484 ms

jquery.zoom.min.js

jquery.zoom.min.js

490 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

491 ms

photoswipe.min.js

photoswipe.min.js

482 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

464 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

498 ms

single-product.min.js

single-product.min.js

496 ms

choices.min.js

choices.min.js

496 ms

jquery.validate.min.js

jquery.validate.min.js

473 ms

universal.js

universal.js

162 ms

fbevents.js

fbevents.js

135 ms

mailcheck.min.js

mailcheck.min.js

364 ms

punycode.min.js

punycode.min.js

368 ms

utils.min.js

utils.min.js

409 ms

wpforms.min.js

wpforms.min.js

411 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX9-p7K4GLs.ttf

90 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX9-p7K4GLs.ttf

121 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX9-p7K4GLs.ttf

148 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

128 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX9-p7K4GLs.ttf

128 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX9-p7K4GLs.ttf

128 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf

127 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX9-p7K4GLs.ttf

161 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX9-p7K4GLs.ttf

167 ms

fa-brands-400.woff

fa-brands-400.woff

486 ms

OrchidNest-Logo.png

OrchidNest-Logo.png

315 ms

Teamrocks1.jpg

Teamrocks1.jpg

81 ms

20190706_Birth_ElleRebuck-04299-scaled.jpeg

20190706_Birth_ElleRebuck-04299-scaled.jpeg

193 ms

doula-services-psekyljws38tahbmwcj3g0yjnmxgai391ul8ngqpiw.jpg

doula-services-psekyljws38tahbmwcj3g0yjnmxgai391ul8ngqpiw.jpg

416 ms

recaptcha__en.js

recaptcha__en.js

30 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

64 ms

Accessibility Review

orchidnest.com accessibility score

78

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

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

orchidnest.com best practices score

92

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

Page has valid source maps

SEO Factors

orchidnest.com SEO score

86

Search Engine Optimization Advices

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

orchidnest.com

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