Tools & Wizards About Us
blomming.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

blomming.com

Blomming Marketplace: Furniture, Fashion, Health and Beauty, Electronics and more

Page Load Speed

2.3 sec in total

First Response

76 ms

Resources Loaded

1.6 sec

Page Rendered

615 ms

blomming.com screenshot

About Website

Visit blomming.com now to see the best up-to-date Blomming content for Italy and also check out these interesting facts you probably never knew about blomming.com

A large catalog of products for all tastes. Buy in complete safety or sell your products in the marketplace, on Facebook, Instagram and in your ecommerce.

Visit blomming.com

Key Findings

We analyzed Blomming.com page load time and found that the first response time was 76 ms 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 45% of websites can load faster.

Performance Metrics

blomming.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

blomming.com

76 ms

www.blomming.com

120 ms

master-a429401b639edbd8f93c828b64c335fe.css

16 ms

master-8db7779bcddcdb717bccf65c3ed30320.css

11 ms

modernizr-eaa399764b1cc9e253b227396a45a514.js

37 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 61% of them (46 requests) were addressed to the original Blomming.com, 11% (8 requests) were made to Getresized.blomming.com and 4% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (757 ms) belongs to the original domain Blomming.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (53%)

Content Size

2.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blomming.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 169.2 kB

  • Original 230.4 kB
  • After minification 225.3 kB
  • After compression 61.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 169.2 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 5.8 kB

  • Original 505.3 kB
  • After minification 499.5 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. Blomming images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 761.3 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 430.8 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 761.3 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 225.1 kB

  • Original 269.3 kB
  • After minification 263.6 kB
  • After compression 44.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. Blomming.com needs all CSS files to be minified and compressed as it can save up to 225.1 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

73

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blomming.com

blomming.com

76 ms

www.blomming.com

www.blomming.com

120 ms

master-a429401b639edbd8f93c828b64c335fe.css

master-a429401b639edbd8f93c828b64c335fe.css

16 ms

master-8db7779bcddcdb717bccf65c3ed30320.css

master-8db7779bcddcdb717bccf65c3ed30320.css

11 ms

modernizr-eaa399764b1cc9e253b227396a45a514.js

modernizr-eaa399764b1cc9e253b227396a45a514.js

37 ms

main-6cf5d71f0bff796fc25a6987bb64e92c.js

main-6cf5d71f0bff796fc25a6987bb64e92c.js

73 ms

translations-d4a05f611e327a98717b49c587b75739.js

translations-d4a05f611e327a98717b49c587b75739.js

66 ms

widget.js

widget.js

66 ms

addthis_widget.js

addthis_widget.js

34 ms

dc.js

dc.js

231 ms

bg-header-logged.jpg

bg-header-logged.jpg

320 ms

logo.png

logo.png

319 ms

bg-wall-90.jpg

bg-wall-90.jpg

323 ms

wall-gradient.png

wall-gradient.png

322 ms

icons-1402565695.png

icons-1402565695.png

320 ms

dot-pattern.png

dot-pattern.png

314 ms

sell-on-facebook.jpg

sell-on-facebook.jpg

324 ms

sell-on-blog.jpg

sell-on-blog.jpg

323 ms

sell-affiliation.jpg

sell-affiliation.jpg

326 ms

sell-on-blomming.jpg

sell-on-blomming.jpg

324 ms

tc.png

tc.png

326 ms

wired.png

wired.png

325 ms

the-next-web.png

the-next-web.png

328 ms

sole-24-ore.png

sole-24-ore.png

332 ms

gartner-2012.png

gartner-2012.png

328 ms

repubblica.png

repubblica.png

757 ms

item.jpg

item.jpg

326 ms

no.png

no.png

328 ms

staff-pick-sx.png

staff-pick-sx.png

330 ms

staff-pick-dx.png

staff-pick-dx.png

330 ms

carousel-1402565695.png

carousel-1402565695.png

332 ms

middle-bottom.png

middle-bottom.png

332 ms

bg_big.jpg

bg_big.jpg

332 ms

iphone-image.png

iphone-image.png

333 ms

app-store.png

app-store.png

333 ms

basic.png

basic.png

344 ms

select-background.png

select-background.png

346 ms

sourcesanspro-regular.woff

sourcesanspro-regular.woff

339 ms

sourcesanspro-light.woff

sourcesanspro-light.woff

339 ms

sourcesanspro-bold.woff

sourcesanspro-bold.woff

338 ms

jquery.blomming.js

jquery.blomming.js

376 ms

all.js

all.js

519 ms

widgets.js

widgets.js

327 ms

plusone.js

plusone.js

436 ms

pinit.js

pinit.js

376 ms

iframe_api

iframe_api

444 ms

f3873c3b40ca744abc7a1d2ec409757d.jpg

f3873c3b40ca744abc7a1d2ec409757d.jpg

356 ms

__utm.gif

__utm.gif

77 ms

ff326f914d7805ca6ef922e0cebb9407.jpg

ff326f914d7805ca6ef922e0cebb9407.jpg

261 ms

9539f2ae3dbaed22bf782e6c858cf679.jpg

9539f2ae3dbaed22bf782e6c858cf679.jpg

255 ms

d3c83cf1d216edca8b1a89df76367702.png

d3c83cf1d216edca8b1a89df76367702.png

262 ms

0f0d3a310d4db0670d9f5f9a327cb145.jpeg

0f0d3a310d4db0670d9f5f9a327cb145.jpeg

260 ms

8fff050147ebbb71a8088acbdf631d53.jpg

8fff050147ebbb71a8088acbdf631d53.jpg

260 ms

98976aadee42069ab62ae42e6a5d50f4.jpg

98976aadee42069ab62ae42e6a5d50f4.jpg

259 ms

69a223cdd62c474a17c3dcb00ea21376.png

69a223cdd62c474a17c3dcb00ea21376.png

261 ms

rooney-heavyitalic.woff

rooney-heavyitalic.woff

97 ms

rooney-regularitalic.woff

rooney-regularitalic.woff

96 ms

rooney-black.woff

rooney-black.woff

96 ms

widget.css

widget.css

42 ms

cart2.css

cart2.css

39 ms

addthis_widget.js

addthis_widget.js

37 ms

pinit_main.js

pinit_main.js

82 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

64 ms

www-widgetapi.js

www-widgetapi.js

100 ms

251 ms

xd_arbiter.php

xd_arbiter.php

236 ms

xd_arbiter.php

xd_arbiter.php

431 ms

nr-885.min.js

nr-885.min.js

122 ms

300lo.json

300lo.json

93 ms

0.json

0.json

52 ms

sh.7c7179124ea24ac6ba46caac.html

sh.7c7179124ea24ac6ba46caac.html

29 ms

sourcesanspro-bold.woff

sourcesanspro-bold.woff

19 ms

9d7e1f7765

9d7e1f7765

55 ms

pixel

pixel

17 ms

pixel

pixel

15 ms

xd_arbiter.php

xd_arbiter.php

140 ms

Accessibility Review

blomming.com accessibility score

75

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

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

ARIA IDs are not unique

Best Practices

blomming.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

blomming.com SEO score

79

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blomming.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Blomming.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

blomming.com

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