Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

inblooom.com

印花樂inBlooom|新台味印花美學,創造美感與共好生活

Page Load Speed

5.4 sec in total

First Response

32 ms

Resources Loaded

3.1 sec

Page Rendered

2.3 sec

inblooom.com screenshot

About Website

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

台灣最具代表性的印花設計品牌,以經典台灣元素作為靈感來源,開發印花設計商品,同時傳遞會共好與環境保護的理念。另有提供手作課程體驗、企業客製服務與圖像授權方案,希望能將美感與創作體驗,以更平易近人的方式,帶進大家的生活裡。

Visit inblooom.com

Key Findings

We analyzed Inblooom.com page load time and found that the first response time was 32 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

inblooom.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value27.4 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value990 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

inblooom.com

32 ms

www.inblooom.com

175 ms

3375562265-css_bundle_v2.css

50 ms

authorization.css

104 ms

jquery.min.js

79 ms

Our browser made a total of 154 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Inblooom.com, 12% (18 requests) were made to Pbs.twimg.com and 8% (12 requests) were made to 2.bp.blogspot.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Az796311.vo.msecnd.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 361.1 kB (11%)

Content Size

3.4 MB

After Optimization

3.1 MB

In fact, the total size of Inblooom.com main page is 3.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. 80% 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. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 189.6 kB

  • Original 226.3 kB
  • After minification 223.0 kB
  • After compression 36.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 189.6 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 13.9 kB

  • Original 2.9 MB
  • After minification 2.9 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. Inblooom images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 157.6 kB

  • Original 301.6 kB
  • After minification 301.6 kB
  • After compression 144.0 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 157.6 kB or 52% of the original size.

CSS Optimization

-0%

Potential reduce by 6 B

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

Requests Breakdown

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

Requests Now

150

After Optimization

89

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

Accessibility Review

inblooom.com accessibility score

84

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

[aria-hidden="true"] elements contain focusable descendents

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

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

inblooom.com SEO score

97

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

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inblooom.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Inblooom.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 Inblooom. 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: