Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

inbloomflowers.com

Same-Day Flower Delivery in Arlington, Plano & Carrollton | In Bloom Flowers

Page Load Speed

3.8 sec in total

First Response

147 ms

Resources Loaded

3.1 sec

Page Rendered

565 ms

About Website

Visit inbloomflowers.com now to see the best up-to-date In Bloom Flowers content for United States and also check out these interesting facts you probably never knew about inbloomflowers.com

In Bloom Flowers, Gifts and More offer same-day delivery from Arlington, Plano, McKinney, Lewisville, Carrollton, & Dallas-Fort Worth areas. Shop online or in our 3 locations...

Visit inbloomflowers.com

Key Findings

We analyzed Inbloomflowers.com page load time and found that the first response time was 147 ms and then it took 3.7 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

inbloomflowers.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value6,190 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.139

79/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

www.inbloomflowers.com

147 ms

www.inbloomflowers.com

240 ms

gtm.js

156 ms

ef-screen.css

104 ms

theme.css

199 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 4% of them (4 requests) were addressed to the original Inbloomflowers.com, 57% (57 requests) were made to Assets.eflorist.com and 8% (8 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Assets.eflorist.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.5 kB (6%)

Content Size

3.1 MB

After Optimization

2.9 MB

In fact, the total size of Inbloomflowers.com main page is 3.1 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. 70% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 123.0 kB

  • Original 151.4 kB
  • After minification 136.5 kB
  • After compression 28.4 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 123.0 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 18.4 kB

  • Original 2.6 MB
  • After minification 2.6 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. In Bloom Flowers images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 41.1 kB

  • Original 197.0 kB
  • After minification 197.0 kB
  • After compression 155.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 41.1 kB or 21% of the original size.

CSS Optimization

-0%

Potential reduce by 5 B

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

Requests Breakdown

Number of requests can be reduced by 38 (45%)

Requests Now

84

After Optimization

46

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

Accessibility Review

inbloomflowers.com accessibility score

78

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

[role]s are not contained by their required parent element

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

inbloomflowers.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

inbloomflowers.com SEO score

93

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

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

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