Tools & Wizards About Us
wed-icity.com screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

wed-icity.com

Wedicity - Destination Wedding Planners

Page Load Speed

1.7 sec in total

First Response

48 ms

Resources Loaded

1.6 sec

Page Rendered

55 ms

wed-icity.com screenshot

About Website

Welcome to wed-icity.com homepage info - get ready to check Wedicity best content right away, or after learning these important things about wed-icity.com

Chicago based Wedding & Event Planner offering full service planning, partial planning and 90-days of details packages!

Visit wed-icity.com

Key Findings

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

Performance Metrics

wed-icity.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value4.1 s

80/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

www.wed-icity.com

48 ms

minified.js

24 ms

focus-within-polyfill.js

53 ms

polyfill.min.js

1022 ms

thunderbolt-commons.81e79c4a.bundle.min.js

38 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Wed-icity.com, 42% (19 requests) were made to Static.parastorage.com and 24% (11 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 805.4 kB (59%)

Content Size

1.4 MB

After Optimization

570.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wed-icity.com main page is 1.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. 40% of websites need less resources to load. HTML takes 915.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 740.8 kB

  • Original 915.1 kB
  • After minification 913.5 kB
  • After compression 174.3 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 740.8 kB or 81% of the original size.

Image Optimization

-9%

Potential reduce by 15.9 kB

  • Original 171.0 kB
  • After minification 155.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. Wedicity images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 48.7 kB

  • Original 289.4 kB
  • After minification 289.3 kB
  • After compression 240.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 48.7 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (42%)

Requests Now

24

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wed-icity.com

www.wed-icity.com

48 ms

minified.js

minified.js

24 ms

focus-within-polyfill.js

focus-within-polyfill.js

53 ms

polyfill.min.js

polyfill.min.js

1022 ms

thunderbolt-commons.81e79c4a.bundle.min.js

thunderbolt-commons.81e79c4a.bundle.min.js

38 ms

main.e8bb44c8.bundle.min.js

main.e8bb44c8.bundle.min.js

38 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

39 ms

lodash.min.js

lodash.min.js

39 ms

react.production.min.js

react.production.min.js

41 ms

react-dom.production.min.js

react-dom.production.min.js

41 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

39 ms

WEDCITY-01-2.png

WEDCITY-01-2.png

93 ms

24a611_7bc150af8eb74c2e930e924762085b0ef000.jpg

24a611_7bc150af8eb74c2e930e924762085b0ef000.jpg

209 ms

Wedicity%20destination%20wedding%20planner%20chicago%20-%20Nikki%20Marie%20Photo.jpg

Wedicity%20destination%20wedding%20planner%20chicago%20-%20Nikki%20Marie%20Photo.jpg

294 ms

A%2BM-410_edited.jpg

A%2BM-410_edited.jpg

142 ms

24a611_1749d69c3df145a9b7d1f8fe9b467b51~mv2.png

24a611_1749d69c3df145a9b7d1f8fe9b467b51~mv2.png

277 ms

24a611_d976d59a34cf49678f982ff4f46ea875~mv2.png

24a611_d976d59a34cf49678f982ff4f46ea875~mv2.png

319 ms

Wedicity%20Featured%20in%20Chicago%20Style%20Weddings_edited.png

Wedicity%20Featured%20in%20Chicago%20Style%20Weddings_edited.png

293 ms

24a611_fe1d1e5bec5649bf9fed9676e8b2bc68~mv2.png

24a611_fe1d1e5bec5649bf9fed9676e8b2bc68~mv2.png

276 ms

24a611_d459b486a7794f3294097d4219878602~mv2.jpg

24a611_d459b486a7794f3294097d4219878602~mv2.jpg

334 ms

bundle.min.js

bundle.min.js

66 ms

file.woff

file.woff

163 ms

file.woff

file.woff

166 ms

iEjm9hVxcattz37Y8gZwVbaDr2DD9WOmTsY4M3S93hU.woff

iEjm9hVxcattz37Y8gZwVbaDr2DD9WOmTsY4M3S93hU.woff

8 ms

iEjm9hVxcattz37Y8gZwVQIBIRsdTZvmhTwexVJEOCE.woff

iEjm9hVxcattz37Y8gZwVQIBIRsdTZvmhTwexVJEOCE.woff

11 ms

cormorant-garamond-v7-latin-ext_latin_cyrillic-regular.woff

cormorant-garamond-v7-latin-ext_latin_cyrillic-regular.woff

26 ms

cormorant-garamond-v7-latin-ext_latin_cyrillic-700.woff

cormorant-garamond-v7-latin-ext_latin_cyrillic-700.woff

21 ms

98 ms

97 ms

111 ms

95 ms

97 ms

93 ms

138 ms

131 ms

134 ms

139 ms

131 ms

deprecation-en.v5.html

deprecation-en.v5.html

3 ms

bolt-performance

bolt-performance

21 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

16 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

3 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

5 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

5 ms

Accessibility Review

wed-icity.com accessibility score

97

Accessibility Issues

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.

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

wed-icity.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

wed-icity.com SEO score

96

Search Engine Optimization Advices

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 Wed-icity.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 Wed-icity.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

wed-icity.com

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