Tools & Wizards About Us
at-berry.jp screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 66

    SEO

    Google-friendlier than
    26% of websites

at-berry.jp

ワキ・二の腕の黒ずみ対策に薬用アットベリー！黒ずみケアクリーム《公式》

Page Load Speed

5.2 sec in total

First Response

1 sec

Resources Loaded

2.8 sec

Page Rendered

1.4 sec

at-berry.jp screenshot

About Website

Welcome to at-berry.jp homepage info - get ready to check At Berry best content for Japan right away, or after learning these important things about at-berry.jp

脇や二の腕などの気になる部分の黒ずみ対策に！薬用アットベリーはワキ・二の腕の黒ずみケアクリーム

Visit at-berry.jp

Key Findings

We analyzed At-berry.jp page load time and found that the first response time was 1 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

at-berry.jp performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.7 s

28/100

10%

Network Requests Diagram

at-berry.jp

1005 ms

style.min.css

193 ms

animate.min.css

354 ms

owl.carousel.min.css

363 ms

perfect-scrollbar.min.css

368 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 89% of them (17 requests) were addressed to the original At-berry.jp, 5% (1 request) were made to Fonts.googleapis.com and 5% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain At-berry.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 175.4 kB (19%)

Content Size

925.6 kB

After Optimization

750.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of At-berry.jp main page is 925.6 kB. 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. Javascripts take 791.1 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 59.2 kB

  • Original 69.0 kB
  • After minification 64.6 kB
  • After compression 9.9 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 59.2 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 4 B

  • Original 3.4 kB
  • After minification 3.4 kB

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. At Berry images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 94.2 kB

  • Original 791.1 kB
  • After minification 791.1 kB
  • After compression 696.8 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 94.2 kB or 12% of the original size.

CSS Optimization

-35%

Potential reduce by 22.0 kB

  • Original 62.1 kB
  • After minification 62.1 kB
  • After compression 40.2 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. At-berry.jp needs all CSS files to be minified and compressed as it can save up to 22.0 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (76%)

Requests Now

17

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

at-berry.jp

at-berry.jp

1005 ms

style.min.css

style.min.css

193 ms

animate.min.css

animate.min.css

354 ms

owl.carousel.min.css

owl.carousel.min.css

363 ms

perfect-scrollbar.min.css

perfect-scrollbar.min.css

368 ms

css

css

44 ms

style.css

style.css

547 ms

jquery.min.js

jquery.min.js

571 ms

jquery-migrate.min.js

jquery-migrate.min.js

376 ms

all.min.js

all.min.js

1574 ms

v4-shims.min.js

v4-shims.min.js

535 ms

owl.carousel.min.js

owl.carousel.min.js

560 ms

owlcarousel2-a11ylayer.min.js

owlcarousel2-a11ylayer.min.js

688 ms

perfect-scrollbar.min.js

perfect-scrollbar.min.js

881 ms

custom.min.js

custom.min.js

883 ms

modal-accessibility.min.js

modal-accessibility.min.js

883 ms

cropped-%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2024-04-09-22.58.56-1.png

cropped-%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2024-04-09-22.58.56-1.png

202 ms

at-berry.jp

at-berry.jp

199 ms

wEO_EBrOk8hQLDvIAF81VvoP.ttf

wEO_EBrOk8hQLDvIAF81VvoP.ttf

22 ms

Accessibility Review

at-berry.jp accessibility score

86

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

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.

Best Practices

at-berry.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

at-berry.jp SEO score

66

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise At-berry.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that At-berry.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

at-berry.jp

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