Tools & Wizards About Us
whitehousebride.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

whitehousebride.com

White House Bride | Edgewater, NJ & Whitehouse Station, NJ Bridal Boutique

Page Load Speed

1.3 sec in total

First Response

71 ms

Resources Loaded

766 ms

Page Rendered

457 ms

whitehousebride.com screenshot

About Website

Visit whitehousebride.com now to see the best up-to-date White House Bride content and also check out these interesting facts you probably never knew about whitehousebride.com

Located in Edgewater and Whitehouse Station, New Jersey White House Bride is a top bridal boutique dedicated to helping customers find the perfect bridal dresses. Come shop our wide selection of desig...

Visit whitehousebride.com

Key Findings

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

Performance Metrics

whitehousebride.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value2,500 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.073

96/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

whitehousebride.com

71 ms

ubl2nhf.css

311 ms

js

75 ms

theme.min.css

29 ms

theme.min.js

93 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 70% of them (26 requests) were addressed to the original Whitehousebride.com, 19% (7 requests) were made to Use.typekit.net and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (311 ms) relates to the external source Use.typekit.net.

Page Optimization Overview & Recommendations

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

Content Size

2.2 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 67.3 kB

  • Original 79.4 kB
  • After minification 58.3 kB
  • After compression 12.1 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 21.1 kB, which is 27% 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 67.3 kB or 85% of the original size.

Image Optimization

-28%

Potential reduce by 342.8 kB

  • Original 1.2 MB
  • After minification 896.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. Obviously, White House Bride needs image optimization as it can save up to 342.8 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-14%

Potential reduce by 88.7 kB

  • Original 655.6 kB
  • After minification 655.6 kB
  • After compression 566.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 88.7 kB or 14% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 226.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.

Requests Breakdown

Number of requests can be reduced by 3 (11%)

Requests Now

27

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whitehousebride.com

whitehousebride.com

71 ms

ubl2nhf.css

ubl2nhf.css

311 ms

js

js

75 ms

theme.min.css

theme.min.css

29 ms

theme.min.js

theme.min.js

93 ms

js

js

124 ms

p.css

p.css

22 ms

fbevents.js

fbevents.js

174 ms

main-logo

main-logo

129 ms

hero_4x_44b60839_dd2a_4301_96cb_7e8cee39cbf3_0b1ebd42_7be9_42f8_9776_a04fa2bfcb85.webp

hero_4x_44b60839_dd2a_4301_96cb_7e8cee39cbf3_0b1ebd42_7be9_42f8_9776_a04fa2bfcb85.webp

111 ms

hero_2x_bdb8c7df_b825_47aa_8202_84f1a209c842_f6658a0b_8e3c_4317_a3b8_6d32790d2aab.webp

hero_2x_bdb8c7df_b825_47aa_8202_84f1a209c842_f6658a0b_8e3c_4317_a3b8_6d32790d2aab.webp

112 ms

edc5c2dd_6a88_4a4f_8513_30c9d9790d53_7de68f92_b182_4540_8af6_4df589912528.webp

edc5c2dd_6a88_4a4f_8513_30c9d9790d53_7de68f92_b182_4540_8af6_4df589912528.webp

207 ms

desktop__5__f5dee7eb_17b3_4759_9918_213de9cbda18.webp

desktop__5__f5dee7eb_17b3_4759_9918_213de9cbda18.webp

207 ms

hero_4_4x_51e7f2cb_df42_414b_8b38_c6cda8854ae5_3a67cf14_2219_4d32_957a_55c2006bed07.webp

hero_4_4x_51e7f2cb_df42_414b_8b38_c6cda8854ae5_3a67cf14_2219_4d32_957a_55c2006bed07.webp

218 ms

hero_4_2x_cd8c222f_8ced_4729_8a8d_985a4bed510c_d890706d_6f97_49e9___ff_08706555ea06.webp

hero_4_2x_cd8c222f_8ced_4729_8a8d_985a4bed510c_d890706d_6f97_49e9___ff_08706555ea06.webp

242 ms

17af86a94aea4478bc438d14917f5cd0.webp

17af86a94aea4478bc438d14917f5cd0.webp

218 ms

516afb011ca640b3935a6468ac68f1a4.webp

516afb011ca640b3935a6468ac68f1a4.webp

243 ms

whitehousebride_edgewater_storefrontsign.webp

whitehousebride_edgewater_storefrontsign.webp

246 ms

whitehousebride_whitehouse_storefrontsign.webp

whitehousebride_whitehouse_storefrontsign.webp

242 ms

featured-designer.jpg

featured-designer.jpg

242 ms

featured-event-mobile.jpg

featured-event-mobile.jpg

271 ms

featured-event.jpg

featured-event.jpg

245 ms

featured-collection1.jpg

featured-collection1.jpg

242 ms

featured-collection2.jpg

featured-collection2.jpg

243 ms

3rd_image.webp

3rd_image.webp

244 ms

featured-collection4.jpg

featured-collection4.jpg

244 ms

brides-new.webp

brides-new.webp

244 ms

additional-logo-footer-logo

additional-logo-footer-logo

247 ms

d

d

36 ms

d

d

113 ms

d

d

133 ms

icomoon.ttf

icomoon.ttf

172 ms

d

d

143 ms

d

d

143 ms

d

d

144 ms

MelindaScript.woff

MelindaScript.woff

172 ms

Syvo-Icomoon.ttf

Syvo-Icomoon.ttf

172 ms

Accessibility Review

whitehousebride.com accessibility score

81

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-hidden="true"] elements contain focusable descendents

High

[role]s are not contained by their required parent element

High

[aria-*] attributes are not valid or misspelled

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

whitehousebride.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

whitehousebride.com SEO score

89

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

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

whitehousebride.com

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