Tools & Wizards About Us
nationalbridalshow.com screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

nationalbridalshow.com

National Bridal Show | February 1-3, 2019 Toronto, ON

Page Load Speed

4.2 sec in total

First Response

64 ms

Resources Loaded

3.9 sec

Page Rendered

239 ms

nationalbridalshow.com screenshot

About Website

Visit nationalbridalshow.com now to see the best up-to-date National Bridal Show content for Canada and also check out these interesting facts you probably never knew about nationalbridalshow.com

One of the biggest bridal shows in Toronto, ON. Connecting couples with Wedding Vendors who truly care about your Special Day!

Visit nationalbridalshow.com

Key Findings

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

Performance Metrics

nationalbridalshow.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value24.2 s

0/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value1,550 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.347

32/100

15%

TTI (Time to Interactive)

Value29.5 s

0/100

10%

Network Requests Diagram

nationalbridalshow.com

64 ms

www.nationalbridalshow.com

615 ms

gtm.js

306 ms

hxnja.css

8 ms

hqyvc.css

46 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 57% of them (58 requests) were addressed to the original Nationalbridalshow.com, 17% (17 requests) were made to Static.xx.fbcdn.net and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 751.9 kB (14%)

Content Size

5.2 MB

After Optimization

4.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nationalbridalshow.com main page is 5.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. Only a small number of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 102.5 kB

  • Original 124.6 kB
  • After minification 117.6 kB
  • After compression 22.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. 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 102.5 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 293.4 kB

  • Original 4.1 MB
  • After minification 3.8 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. National Bridal Show images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 353.2 kB

  • Original 964.8 kB
  • After minification 964.8 kB
  • After compression 611.6 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 353.2 kB or 37% of the original size.

CSS Optimization

-5%

Potential reduce by 2.8 kB

  • Original 60.7 kB
  • After minification 60.7 kB
  • After compression 57.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. Nationalbridalshow.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 44 (49%)

Requests Now

89

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nationalbridalshow.com

nationalbridalshow.com

64 ms

www.nationalbridalshow.com

www.nationalbridalshow.com

615 ms

gtm.js

gtm.js

306 ms

hxnja.css

hxnja.css

8 ms

hqyvc.css

hqyvc.css

46 ms

css

css

85 ms

5ulvt.css

5ulvt.css

71 ms

page.js

page.js

89 ms

hqyvc.js

hqyvc.js

89 ms

hqyvc.js

hqyvc.js

70 ms

gpt.js

gpt.js

369 ms

dpx.js

dpx.js

73 ms

4bld1.css

4bld1.css

69 ms

index.js

index.js

70 ms

index.js

index.js

69 ms

api.js

api.js

151 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

72 ms

wp-polyfill.min.js

wp-polyfill.min.js

87 ms

index.js

index.js

77 ms

ubermenu.min.js

ubermenu.min.js

79 ms

slick.min.js

slick.min.js

78 ms

wppsac-public.js

wppsac-public.js

85 ms

imagesloaded.min.js

imagesloaded.min.js

86 ms

masonry.min.js

masonry.min.js

147 ms

jquery.masonry.min.js

jquery.masonry.min.js

145 ms

envira-min.js

envira-min.js

278 ms

sbi-scripts.min.js

sbi-scripts.min.js

149 ms

frontend.js

frontend.js

149 ms

video.php

video.php

1950 ms

logo.png

logo.png

285 ms

Unknown-2-150x150.png

Unknown-2-150x150.png

287 ms

tp-150x150.jpg

tp-150x150.jpg

285 ms

Whistle-Bear-Wedding-in-Cambridge-150x150.jpg

Whistle-Bear-Wedding-in-Cambridge-150x150.jpg

284 ms

Untitled-design-1-150x150.png

Untitled-design-1-150x150.png

284 ms

ADA-Photography-314934-150x150.jpg

ADA-Photography-314934-150x150.jpg

284 ms

Contests-150x150.jpg

Contests-150x150.jpg

310 ms

header1-menu.jpg

header1-menu.jpg

311 ms

Untitled-design-6.png

Untitled-design-6.png

543 ms

logo_header.png

logo_header.png

310 ms

Unknown-2.png

Unknown-2.png

541 ms

tp.jpg

tp.jpg

309 ms

Whistle-Bear-Wedding-in-Cambridge.jpg

Whistle-Bear-Wedding-in-Cambridge.jpg

503 ms

kristina-evstifeeva-450542-unsplash.jpg

kristina-evstifeeva-450542-unsplash.jpg

401 ms

DA-Photography-371442.jpg

DA-Photography-371442.jpg

503 ms

shutterstock_630708191.jpg

shutterstock_630708191.jpg

540 ms

Resort-1.jpg

Resort-1.jpg

544 ms

redd-angelo-605315-unsplash.jpg

redd-angelo-605315-unsplash.jpg

546 ms

Suhaag-PreWeddingTalks-759x500.jpg

Suhaag-PreWeddingTalks-759x500.jpg

543 ms

fuji3.jpg

fuji3.jpg

544 ms

sponsor-logos-4-640x480_c.png

sponsor-logos-4-640x480_c.png

545 ms

SPONSOR-LOGO-1-640x480_c.png

SPONSOR-LOGO-1-640x480_c.png

545 ms

sponsor-logos-1-640x480_c.png

sponsor-logos-1-640x480_c.png

547 ms

Untitled-design-2-1024x1024-640x480_c.jpg

Untitled-design-2-1024x1024-640x480_c.jpg

546 ms

sponsor-logos-3-1-640x480_c.png

sponsor-logos-3-1-640x480_c.png

548 ms

Untitled-design-19-1-640x480_c.png

Untitled-design-19-1-640x480_c.png

548 ms

sponsor-logos-4-1-640x480_c.png

sponsor-logos-4-1-640x480_c.png

548 ms

SPONSOR-LOGO-2-640x480_c.png

SPONSOR-LOGO-2-640x480_c.png

548 ms

Untitled-design-24-640x480_c.png

Untitled-design-24-640x480_c.png

547 ms

SPONSOR-LOGO-640x480_c.png

SPONSOR-LOGO-640x480_c.png

549 ms

metroland-logo.png

metroland-logo.png

549 ms

sm.25.html

sm.25.html

280 ms

eso.BRQnzO8v.js

eso.BRQnzO8v.js

304 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

362 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

397 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

496 ms

recaptcha__en.js

recaptcha__en.js

536 ms

ajax-loader.gif

ajax-loader.gif

1215 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

388 ms

z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff1GhDuXMQg.ttf

z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff1GhDuXMQg.ttf

238 ms

serioussliderglyphs.ttf

serioussliderglyphs.ttf

386 ms

socials.woff

socials.woff

386 ms

blocks.woff

blocks.woff

386 ms

pubads_impl.js

pubads_impl.js

283 ms

ppub_config

ppub_config

425 ms

js

js

127 ms

analytics.js

analytics.js

261 ms

collect

collect

168 ms

ads

ads

306 ms

container.html

container.html

24 ms

collect

collect

27 ms

ga-audiences

ga-audiences

22 ms

NqJuxoKe2Wd.css

NqJuxoKe2Wd.css

18 ms

ecWx_AzRtFn.css

ecWx_AzRtFn.css

29 ms

VWDhCULazb5.js

VWDhCULazb5.js

29 ms

dC-ahKfTBu9.js

dC-ahKfTBu9.js

96 ms

BuRfUkq6WA7.js

BuRfUkq6WA7.js

99 ms

bBbuBSEiTy3.js

bBbuBSEiTy3.js

97 ms

4r8pcxnOs4K.js

4r8pcxnOs4K.js

96 ms

fizLvmGpwM1.js

fizLvmGpwM1.js

99 ms

-7iezwCfvue.js

-7iezwCfvue.js

97 ms

OYZt-SkRdeX.js

OYZt-SkRdeX.js

97 ms

XYa8aMBgGYr.js

XYa8aMBgGYr.js

125 ms

MxM-QUO1cq3.js

MxM-QUO1cq3.js

124 ms

29786505_10156392026218374_6440036158767366144_n.jpg

29786505_10156392026218374_6440036158767366144_n.jpg

69 ms

326797409_908839646963662_372565459362563114_n.png

326797409_908839646963662_372565459362563114_n.png

43 ms

rQNJ8ig3q3f.js

rQNJ8ig3q3f.js

45 ms

PbZ9XhPJHr4.js

PbZ9XhPJHr4.js

45 ms

css;base64,

css;base64,

16 ms

gkLj31gU23I.css

gkLj31gU23I.css

39 ms

SWhawEjeLCn.png

SWhawEjeLCn.png

39 ms

vwOUmvzU_7P.png

vwOUmvzU_7P.png

37 ms

Accessibility Review

nationalbridalshow.com accessibility score

85

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

button, link, and menuitem elements do not have accessible names.

High

ARIA input fields do not have accessible names

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

nationalbridalshow.com SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

nationalbridalshow.com

Open Graph description is not detected on the main page of National Bridal Show. 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: