Tools & Wizards About Us

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

inblooom.com

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

Page Load Speed

5 sec in total

First Response

44 ms

Resources Loaded

3.8 sec

Page Rendered

1.2 sec

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 44 ms and then it took 5 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

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value5,740 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

inblooom.com

44 ms

www.inblooom.com

1595 ms

common-5500010b0eb5a10ac407ea577c5c067fc3609b82543046f9b2c67b2ab5842684.css

18 ms

theme_varm-a14d2fda1dd88d81da8ac8ed65055cb2f372d8815e43f35efa29abe3f39bc6cd.css

35 ms

intl_tel_input-1d78fdf5.css

61 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Inblooom.com, 46% (12 requests) were made to Cdn.shoplineapp.com and 15% (4 requests) were made to Static.shoplineapp.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Img.shoplineapp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 708.9 kB (21%)

Content Size

3.3 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inblooom.com main page is 3.3 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. 35% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 703.5 kB

  • Original 817.9 kB
  • After minification 686.1 kB
  • After compression 114.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. This page needs HTML code to be minified as it can gain 131.7 kB, which is 16% 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 703.5 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 3.6 kB

  • Original 1.0 MB
  • After minification 1.0 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

-0%

Potential reduce by 194 B

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.3 MB

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.

CSS Optimization

-1%

Potential reduce by 1.5 kB

  • Original 161.0 kB
  • After minification 161.0 kB
  • After compression 159.4 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 10 (45%)

Requests Now

22

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 22 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 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

inblooom.com accessibility score

65

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

Image elements do not have [alt] attributes

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

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

inblooom.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

inblooom.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    ZH

  • Encoding

    N/A

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 it does not match the claimed Chinese language. Our system also found out that Inblooom.com main page’s claimed encoding is . 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

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