Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

donoban.jp

人気レディースファッション通販サイト Donoban - ドノバン 【公式サイト】

Page Load Speed

7.6 sec in total

First Response

706 ms

Resources Loaded

6.3 sec

Page Rendered

632 ms

donoban.jp screenshot

About Website

Visit donoban.jp now to see the best up-to-date Donoban content and also check out these interesting facts you probably never knew about donoban.jp

レディースファッション通販サイト Donoban‐ドノバン。 エイジレスで自分らしさを大切にしたい全ての女性へ。 リーズナブルにトレンドファッションアイテムが購入できる20代・30代・40代へ向けたファッション通販サイトです。

Visit donoban.jp

Key Findings

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

Performance Metrics

donoban.jp performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value24.7 s

0/100

25%

SI (Speed Index)

Value17.4 s

0/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.728

6/100

15%

TTI (Time to Interactive)

Value30.6 s

0/100

10%

Network Requests Diagram

donoban.jp

706 ms

default_system_pc.css

517 ms

jquery.js

1022 ms

application.js

689 ms

cmn.css

348 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 17% of them (23 requests) were addressed to the original Donoban.jp, 44% (58 requests) were made to Rakuten.ne.jp and 30% (40 requests) were made to Image.rakuten.co.jp. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Rakuten.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 506.3 kB (7%)

Content Size

7.3 MB

After Optimization

6.8 MB

In fact, the total size of Donoban.jp main page is 7.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. 70% of websites need less resources to load. Images take 6.7 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 33.9 kB

  • Original 42.3 kB
  • After minification 41.6 kB
  • After compression 8.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. 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 33.9 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 77.7 kB

  • Original 6.7 MB
  • After minification 6.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. Donoban images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 128.5 kB

  • Original 199.8 kB
  • After minification 196.5 kB
  • After compression 71.3 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 128.5 kB or 64% of the original size.

CSS Optimization

-85%

Potential reduce by 266.3 kB

  • Original 312.1 kB
  • After minification 286.3 kB
  • After compression 45.8 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. Donoban.jp needs all CSS files to be minified and compressed as it can save up to 266.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (14%)

Requests Now

102

After Optimization

88

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

Accessibility Review

donoban.jp accessibility score

72

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

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.

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

High

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

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

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

Missing source maps for large first-party JavaScript

SEO Factors

donoban.jp SEO score

82

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

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 doesn't use 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 Donoban.jp 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 Donoban.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

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