Access combi.co.jp. ベビー用品のコンビ株式会社

combi.co.jp screenshot

1

Performance

Renders faster than
19% of other websites
79

Accessibility

Visual factors better than
that of 48% of websites
75

Best Practices

More advanced features
available than in
36% of websites
85

SEO

Google-friendlier than
56% of websites

First Response

709 ms

Resources Loaded

16.1 sec

Page Rendered

1.6 sec

combi.co.jp screenshot

About Website

Visit combi.co.jp now to see the best up-to-date Combi content for Japan and also check out these interesting facts you probably never knew about combi.co.jp

ベビー用品のコンビ株式会社。コンビはベビーカーやチャイルドシートをはじめ、赤ちゃんに安全で高品質なベビー用品を開発・販売しています。育児の感動を創造し支援する企業姿勢を軸に、健康関連用品を含めた事業展開をしています。

Visit combi.co.jp

Key Findings

We analyzed Combi.co.jp page load time and found that the first response time was 709 ms and then it took 17.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value17.6 s

0/100

25%

SI (Speed Index)

Value23.5 s

0/100

10%

TBT (Total Blocking Time)

Value13,780 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.998

2/100

15%

TTI (Time to Interactive)

Value30.1 s

0/100

10%

combi.co.jp

709 ms

www.combi.co.jp

2586 ms

colorbox.css

321 ms

import.css

319 ms

import.css

333 ms

Our browser made a total of 228 requests to load all elements on the main page. We found that 85% of them (193 requests) were addressed to the original Combi.co.jp, 2% (4 requests) were made to Img.combibaby.com and 2% (4 requests) were made to Tag.ladsp.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Combi.co.jp.

Content Size

3.4 MB

After Optimization

2.8 MB

In fact, the total size of Combi.co.jp 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. 40% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 91.1 kB

Original 104.4 kB
After minification 66.5 kB
After compression 13.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 37.9 kB, which is 36% 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 91.1 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 122.0 kB

Original 2.8 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. Combi images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 234.1 kB

Original 363.6 kB
After minification 340.2 kB
After compression 129.5 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 234.1 kB or 64% of the original size.

CSS Optimization

-88%

Potential reduce by 168.9 kB

Original 192.8 kB
After minification 132.1 kB
After compression 23.9 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. Combi.co.jp needs all CSS files to be minified and compressed as it can save up to 168.9 kB or 88% of the original size.

Requests Now

223

After Optimization

116

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

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

High

ARIA IDs are not unique

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Links do not have a discernible name

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

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links are not crawlable

High

robots.txt is not valid

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Combi.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Combi.co.jp 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

combi.co.jp

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