Tools & Wizards About Us
inbloom.info screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

inbloom.info

Wedding flowers from CorvallisBride.com, your source for wedding flowers and wedding professionals in Oregon

Page Load Speed

466 ms in total

First Response

102 ms

Resources Loaded

252 ms

Page Rendered

112 ms

inbloom.info screenshot

About Website

Welcome to inbloom.info homepage info - get ready to check Inbloom best content right away, or after learning these important things about inbloom.info

CorvallisBride.com, a service of Expressions In Bloom. Our goal is to provide you with Magic on your wedding day. Your link to the finest.

Visit inbloom.info

Key Findings

We analyzed Inbloom.info page load time and found that the first response time was 102 ms and then it took 364 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

inbloom.info performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value0.8 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

inbloom.info

102 ms

style.css

38 ms

urchin.js

7 ms

97839.js

101 ms

logo3.gif

69 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 67% of them (6 requests) were addressed to the original Inbloom.info, 22% (2 requests) were made to Google-analytics.com and 11% (1 request) were made to Static.getclicky.com. The less responsive or slowest element that took the longest time to load (102 ms) belongs to the original domain Inbloom.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 14.4 kB (40%)

Content Size

36.5 kB

After Optimization

22.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inbloom.info main page is 36.5 kB. 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 10% of websites need less resources to load. HTML takes 12.3 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 9.2 kB

  • Original 12.3 kB
  • After minification 10.7 kB
  • After compression 3.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 1.6 kB, which is 13% 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 9.2 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 370 B

  • Original 12.3 kB
  • After minification 12.0 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. Inbloom images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 971 B

  • Original 6.8 kB
  • After minification 6.8 kB
  • After compression 5.9 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 971 B or 14% of the original size.

CSS Optimization

-78%

Potential reduce by 3.9 kB

  • Original 5.0 kB
  • After minification 4.1 kB
  • After compression 1.1 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. Inbloom.info needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inbloom. According to our analytics all requests are already optimized.

Network Requests Diagram

inbloom.info

inbloom.info

102 ms

style.css

style.css

38 ms

urchin.js

urchin.js

7 ms

97839.js

97839.js

101 ms

logo3.gif

logo3.gif

69 ms

WFB26-11A.jpg

WFB26-11A.jpg

71 ms

__utm.gif

__utm.gif

4 ms

wrapperback.gif

wrapperback.gif

33 ms

WFB26-11a.jpg

WFB26-11a.jpg

43 ms

Accessibility Review

inbloom.info accessibility score

63

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

inbloom.info best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

inbloom.info SEO score

62

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inbloom.info 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 Inbloom.info main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

inbloom.info

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