Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

angeliebe.co.jp

マタニティウェア・授乳服通販| エンジェリーベ 公式

Page Load Speed

12.9 sec in total

First Response

1.4 sec

Resources Loaded

9.8 sec

Page Rendered

1.6 sec

About Website

Welcome to angeliebe.co.jp homepage info - get ready to check Angeliebe best content for Japan right away, or after learning these important things about angeliebe.co.jp

マタニティウェア・ベビーウェア通販の老舗【エンジェリーベ】へようこそ。​おしゃれで機能的なマタニティウェア、授乳服、ベビーウェア、オリジナル&​ハイクオリティアイテムを豊富に取りそろえています。

Visit angeliebe.co.jp

Key Findings

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

Performance Metrics

angeliebe.co.jp performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

angeliebe.co.jp

1436 ms

a.js

36 ms

gyr.min.js

504 ms

jquery.alerts.css

346 ms

import.css

344 ms

Our browser made a total of 204 requests to load all elements on the main page. We found that 73% of them (148 requests) were addressed to the original Angeliebe.co.jp, 18% (37 requests) were made to Ir0.mobify.com and 3% (6 requests) were made to Api.flipdesk.jp. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source D2gyc6a6aulhmk.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (45%)

Content Size

3.1 MB

After Optimization

1.7 MB

In fact, the total size of Angeliebe.co.jp 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 102.2 kB

  • Original 120.0 kB
  • After minification 95.1 kB
  • After compression 17.8 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 24.9 kB, which is 21% 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 102.2 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 59.7 kB

  • Original 1.4 MB
  • After minification 1.3 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. Angeliebe images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 861.4 kB

  • Original 1.1 MB
  • After minification 902.6 kB
  • After compression 287.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 861.4 kB or 75% of the original size.

CSS Optimization

-89%

Potential reduce by 350.0 kB

  • Original 394.5 kB
  • After minification 336.3 kB
  • After compression 44.5 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. Angeliebe.co.jp needs all CSS files to be minified and compressed as it can save up to 350.0 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (26%)

Requests Now

201

After Optimization

149

The browser has sent 201 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Angeliebe. 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 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

angeliebe.co.jp accessibility score

71

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 input fields do not have accessible names

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

Form elements do not have associated labels

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

angeliebe.co.jp 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

angeliebe.co.jp SEO score

77

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

High

robots.txt is not valid

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

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Angeliebe.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 Angeliebe.co.jp main page’s claimed encoding is shift_jis. 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 description is not detected on the main page of Angeliebe. 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: