Tools & Wizards About Us
downtownindianapolisweddings.com screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

downtownindianapolisweddings.com

Downtown Indianapolis Weddings | The Grand Hall at Historic Union Station

Page Load Speed

1.5 sec in total

First Response

20 ms

Resources Loaded

1.1 sec

Page Rendered

347 ms

downtownindianapolisweddings.com screenshot

About Website

Welcome to downtownindianapolisweddings.com homepage info - get ready to check Downtown Indianapolis Weddings best content right away, or after learning these important things about downtownindianapolisweddings.com

Say "I Do" to the perfect downtown Indianapolis Wedding Location at The Grand Hall at Historic Union Station. We can plan your perfect Indianapolis wedding.

Visit downtownindianapolisweddings.com

Key Findings

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

Performance Metrics

downtownindianapolisweddings.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.23

54/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

Network Requests Diagram

downtownindianapolisweddings.com

20 ms

www.downtownindianapolisweddings.com

64 ms

normalize.css

6 ms

handsome.css

19 ms

jquery-ui.css

17 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 19% of them (19 requests) were addressed to the original Downtownindianapolisweddings.com, 16% (16 requests) were made to Images.letgroup.com and 15% (15 requests) were made to C-tiles.locationiq.com. The less responsive or slowest element that took the longest time to load (586 ms) relates to the external source A-tiles.locationiq.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 166.1 kB (7%)

Content Size

2.5 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Downtownindianapolisweddings.com main page is 2.5 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. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 18.9 kB

  • Original 24.4 kB
  • After minification 23.4 kB
  • After compression 5.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 18.9 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 142.0 kB

  • Original 2.4 MB
  • After minification 2.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. Downtown Indianapolis Weddings images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 5.1 kB

  • Original 126.1 kB
  • After minification 126.1 kB
  • After compression 121.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 165 B

  • Original 2.4 kB
  • After minification 2.4 kB
  • After compression 2.2 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. Downtownindianapolisweddings.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

91

After Optimization

61

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

downtownindianapolisweddings.com

downtownindianapolisweddings.com

20 ms

www.downtownindianapolisweddings.com

www.downtownindianapolisweddings.com

64 ms

normalize.css

normalize.css

6 ms

handsome.css

handsome.css

19 ms

jquery-ui.css

jquery-ui.css

17 ms

styles.css

styles.css

23 ms

slick.css

slick.css

66 ms

css

css

58 ms

modernizr.js

modernizr.js

73 ms

nivo.theme.comb.3.0.1.min.css

nivo.theme.comb.3.0.1.min.css

83 ms

leaflet.css

leaflet.css

67 ms

leaflet-gesture-handling.min.css

leaflet-gesture-handling.min.css

86 ms

jquery.min.js

jquery.min.js

57 ms

jquery-ui.min.js

jquery-ui.min.js

69 ms

jquery.migrate.js

jquery.migrate.js

82 ms

jquery.backstretch.min-v2.js

jquery.backstretch.min-v2.js

81 ms

jquery.slick.js

jquery.slick.js

80 ms

jquery.magnific.js

jquery.magnific.js

81 ms

masonry.min.js

masonry.min.js

20 ms

jquery.validate.js

jquery.validate.js

56 ms

jquery.easing.js

jquery.easing.js

22 ms

jquery.form.js

jquery.form.js

50 ms

scripts.js

scripts.js

29 ms

js

js

83 ms

leaflet.js

leaflet.js

119 ms

leaflet-unwired.js

leaflet-unwired.js

119 ms

logo-cp.png

logo-cp.png

12 ms

cmsimg_1501138948.jpg

cmsimg_1501138948.jpg

172 ms

cmsimg_1501139411-0.jpg

cmsimg_1501139411-0.jpg

174 ms

cmsimg_1501139488.jpg

cmsimg_1501139488.jpg

171 ms

cmsimg_1501139548.jpg

cmsimg_1501139548.jpg

172 ms

cmsimg_1501139623.jpg

cmsimg_1501139623.jpg

171 ms

spg_1501140202.jpg

spg_1501140202.jpg

171 ms

jqg_1658337093.jpg

jqg_1658337093.jpg

322 ms

jqg_1724860298.jpg

jqg_1724860298.jpg

174 ms

jqg_1501142846.jpg

jqg_1501142846.jpg

174 ms

jqg_1724860298-0.jpg

jqg_1724860298-0.jpg

175 ms

jqg_1658337094-0.jpg

jqg_1658337094-0.jpg

262 ms

jqg_1501142881.jpg

jqg_1501142881.jpg

187 ms

jqg_1724860299.jpg

jqg_1724860299.jpg

186 ms

leaflet-gesture-handling.min.css

leaflet-gesture-handling.min.css

35 ms

leaflet-gesture-handling@1.2.2

leaflet-gesture-handling@1.2.2

124 ms

logo.png

logo.png

128 ms

bknd-section-home.jpg

bknd-section-home.jpg

31 ms

slider-nav.png

slider-nav.png

29 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

32 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

114 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

119 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

119 ms

leaflet-gesture-handling.min.js

leaflet-gesture-handling.min.js

24 ms

ajax-loader.gif

ajax-loader.gif

49 ms

nav-left.png

nav-left.png

33 ms

1728.png

1728.png

182 ms

1729.png

1729.png

198 ms

1728.png

1728.png

137 ms

jqg_1502306537.jpg

jqg_1502306537.jpg

62 ms

jqg_1502305922.jpg

jqg_1502305922.jpg

141 ms

jqg_1502306414.jpg

jqg_1502306414.jpg

143 ms

1728.png

1728.png

269 ms

1728.png

1728.png

249 ms

1729.png

1729.png

373 ms

1729.png

1729.png

270 ms

99468.png

99468.png

560 ms

99467.png

99467.png

586 ms

99467.png

99467.png

477 ms

99468.png

99468.png

485 ms

99468.png

99468.png

495 ms

1729.png

1729.png

137 ms

1728.png

1728.png

146 ms

1729.png

1729.png

137 ms

99467.png

99467.png

258 ms

99468.png

99468.png

324 ms

99467.png

99467.png

314 ms

99468.png

99468.png

316 ms

nav-right.png

nav-right.png

46 ms

pin.png

pin.png

28 ms

1729.png

1729.png

164 ms

1729.png

1729.png

126 ms

1728.png

1728.png

153 ms

1728.png

1728.png

127 ms

99467.png

99467.png

352 ms

99468.png

99468.png

304 ms

99468.png

99468.png

358 ms

99467.png

99467.png

355 ms

99467.png

99467.png

375 ms

6216.png

6216.png

302 ms

6217.png

6217.png

395 ms

6216.png

6216.png

311 ms

6217.png

6217.png

351 ms

6216.png

6216.png

268 ms

6217.png

6217.png

168 ms

6217.png

6217.png

160 ms

6216.png

6216.png

151 ms

6216.png

6216.png

176 ms

6217.png

6217.png

201 ms

6216.png

6216.png

262 ms

6216.png

6216.png

251 ms

6217.png

6217.png

190 ms

6217.png

6217.png

216 ms

Accessibility Review

downtownindianapolisweddings.com accessibility score

82

Accessibility Issues

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

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

downtownindianapolisweddings.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

downtownindianapolisweddings.com SEO score

83

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

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

downtownindianapolisweddings.com

Open Graph description is not detected on the main page of Downtown Indianapolis Weddings. 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: