Tools & Wizards About Us
eventsinbloom.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

eventsinbloom.com

Wedding Decorations | Events In Bloom | United States

Page Load Speed

3.3 sec in total

First Response

1.1 sec

Resources Loaded

2.1 sec

Page Rendered

74 ms

eventsinbloom.com screenshot

About Website

Visit eventsinbloom.com now to see the best up-to-date Events In Bloom content and also check out these interesting facts you probably never knew about eventsinbloom.com

Houston based provider of luxury flowers, linens, lounge and other event decorations for weddings and other social events.

Visit eventsinbloom.com

Key Findings

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

Performance Metrics

eventsinbloom.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value2,170 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.207

60/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

www.eventsinbloom.com

1091 ms

minified.js

40 ms

focus-within-polyfill.js

37 ms

polyfill.min.js

34 ms

thunderbolt-commons.d984b95d.bundle.min.js

26 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Eventsinbloom.com, 35% (19 requests) were made to Static.parastorage.com and 35% (19 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Eventsinbloom.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 450.4 kB (20%)

Content Size

2.2 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Eventsinbloom.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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 240.4 kB

  • Original 318.1 kB
  • After minification 316.4 kB
  • After compression 77.7 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 240.4 kB or 76% of the original size.

Image Optimization

-12%

Potential reduce by 207.3 kB

  • Original 1.7 MB
  • After minification 1.5 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. Obviously, Events In Bloom needs image optimization as it can save up to 207.3 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 2.7 kB

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

Requests Breakdown

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

Requests Now

34

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Events In Bloom. 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.eventsinbloom.com

www.eventsinbloom.com

1091 ms

minified.js

minified.js

40 ms

focus-within-polyfill.js

focus-within-polyfill.js

37 ms

polyfill.min.js

polyfill.min.js

34 ms

thunderbolt-commons.d984b95d.bundle.min.js

thunderbolt-commons.d984b95d.bundle.min.js

26 ms

main.f286c407.bundle.min.js

main.f286c407.bundle.min.js

146 ms

lodash.min.js

lodash.min.js

148 ms

react.production.min.js

react.production.min.js

144 ms

react-dom.production.min.js

react-dom.production.min.js

148 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

146 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

146 ms

7e57c8_3140c61c8aaa4b10a2fc648c696117b7~mv2.jpg

7e57c8_3140c61c8aaa4b10a2fc648c696117b7~mv2.jpg

310 ms

bundle.min.js

bundle.min.js

62 ms

7e57c8_9d76b738f76645b5a2b13ca404e0bb8f~mv2.jpg

7e57c8_9d76b738f76645b5a2b13ca404e0bb8f~mv2.jpg

281 ms

7e57c8_6e402689cda74b58bca71acc49c49f2e~mv2.png

7e57c8_6e402689cda74b58bca71acc49c49f2e~mv2.png

293 ms

7e57c8_56c7659dc6d54044918d4dd336a27a85~mv2.png

7e57c8_56c7659dc6d54044918d4dd336a27a85~mv2.png

282 ms

7e57c8_e2cc2a129bb547799fd1c1d1ccf0721c~mv2_d_1494_2662_s_2.png

7e57c8_e2cc2a129bb547799fd1c1d1ccf0721c~mv2_d_1494_2662_s_2.png

95 ms

7e57c8_60b69dc139244d5d9dc00437b4202835~mv2.jpeg

7e57c8_60b69dc139244d5d9dc00437b4202835~mv2.jpeg

45 ms

7e57c8_3e9b496e90f945a884ed87b5d1c745d6~mv2.png

7e57c8_3e9b496e90f945a884ed87b5d1c745d6~mv2.png

95 ms

7e57c8_c51613ad40584309b9834d45f5f33e86~mv2_d_3960_2640_s_4_2.jpg

7e57c8_c51613ad40584309b9834d45f5f33e86~mv2_d_3960_2640_s_4_2.jpg

320 ms

7e57c8_d9180651d5a94c17bef58fd51315917f~mv2.jpeg

7e57c8_d9180651d5a94c17bef58fd51315917f~mv2.jpeg

268 ms

7e57c8_4db7362b9b2841bcbc25f066a024d2c6~mv2.jpg

7e57c8_4db7362b9b2841bcbc25f066a024d2c6~mv2.jpg

519 ms

7e57c8_83c4df955beb4c8783fec5728e5ec9b6~mv2.jpg

7e57c8_83c4df955beb4c8783fec5728e5ec9b6~mv2.jpg

571 ms

7e57c8_7472a70cdc6b45d29f9f0f9f2c753db2~mv2.jpg

7e57c8_7472a70cdc6b45d29f9f0f9f2c753db2~mv2.jpg

550 ms

7e57c8_9f4651adef2a4a498209af0a40b33a99~mv2.jpg

7e57c8_9f4651adef2a4a498209af0a40b33a99~mv2.jpg

498 ms

7e57c8_3fabbae2aea5462d8ee4ecb620b52504~mv2.jpg

7e57c8_3fabbae2aea5462d8ee4ecb620b52504~mv2.jpg

518 ms

7e57c8_3140c61c8aaa4b10a2fc648c696117b7~mv2.jpg

7e57c8_3140c61c8aaa4b10a2fc648c696117b7~mv2.jpg

508 ms

7e57c8_c4f895be6cc943078cc798c539638a47~mv2.jpg

7e57c8_c4f895be6cc943078cc798c539638a47~mv2.jpg

779 ms

7e57c8_8011f57c0e5d4122850b5a3b4604b1ea~mv2.jpg

7e57c8_8011f57c0e5d4122850b5a3b4604b1ea~mv2.jpg

775 ms

7e57c8_11061040c5ef4a788cdd067bca01f90a~mv2.jpg

7e57c8_11061040c5ef4a788cdd067bca01f90a~mv2.jpg

780 ms

7e57c8_37e5e7bb0d9b4e0b837cd9a826bcc18d~mv2.jpg

7e57c8_37e5e7bb0d9b4e0b837cd9a826bcc18d~mv2.jpg

742 ms

114 ms

129 ms

136 ms

121 ms

136 ms

134 ms

166 ms

160 ms

160 ms

168 ms

168 ms

162 ms

03805817-4611-4dbc-8c65-0f73031c3973.woff

03805817-4611-4dbc-8c65-0f73031c3973.woff

23 ms

bc176270-17fa-4c78-a343-9fe52824e501.woff

bc176270-17fa-4c78-a343-9fe52824e501.woff

21 ms

07d62b21-8d7a-4c36-be86-d32ab1089972.woff

07d62b21-8d7a-4c36-be86-d32ab1089972.woff

21 ms

a9e95a29-98a7-404a-90ee-1929ad09c696.woff

a9e95a29-98a7-404a-90ee-1929ad09c696.woff

21 ms

deprecation-en.v5.html

deprecation-en.v5.html

11 ms

bolt-performance

bolt-performance

26 ms

deprecation-style.v5.css

deprecation-style.v5.css

4 ms

right-arrow.svg

right-arrow.svg

15 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

7 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

7 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

4 ms

Accessibility Review

eventsinbloom.com accessibility score

96

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.

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

eventsinbloom.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

eventsinbloom.com SEO score

100

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

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

eventsinbloom.com

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