Tools & Wizards About Us
peachbloom.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

peachbloom.com

東京の帽子専門店 【PeachBloom】 ピーチブルーム| 帽子デザイナー入澤 恭子の帽子オーダーメイド・販売・帽子の専門店

Page Load Speed

8.8 sec in total

First Response

653 ms

Resources Loaded

7.9 sec

Page Rendered

295 ms

peachbloom.com screenshot

About Website

Welcome to peachbloom.com homepage info - get ready to check Peach Bloom best content right away, or after learning these important things about peachbloom.com

帽子専門店PeachBloom（ピーチブルーム）はレディース帽子を中心に大きいサイズの帽子、小さいサイズの帽子、またオーダーメイドでの販売もしています。キャスケット、ハット、つば広帽子、ニット帽など種類も豊富に取り揃えています。

Visit peachbloom.com

Key Findings

We analyzed Peachbloom.com page load time and found that the first response time was 653 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

peachbloom.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

peachbloom.com

653 ms

vkExUnit_style.css

174 ms

header-top.css

343 ms

style.min.css

517 ms

style.css

343 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 93% of them (65 requests) were addressed to the original Peachbloom.com, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

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

Content Size

514.3 kB

After Optimization

415.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Peachbloom.com main page is 514.3 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. 45% of websites need less resources to load. Images take 243.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 38.6 kB

  • Original 48.1 kB
  • After minification 47.3 kB
  • After compression 9.5 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 38.6 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 76 B

  • Original 243.6 kB
  • After minification 243.5 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. Peach Bloom images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 10.4 kB

  • Original 61.5 kB
  • After minification 61.5 kB
  • After compression 51.1 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 10.4 kB or 17% of the original size.

CSS Optimization

-31%

Potential reduce by 49.3 kB

  • Original 161.0 kB
  • After minification 160.8 kB
  • After compression 111.7 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. Peachbloom.com needs all CSS files to be minified and compressed as it can save up to 49.3 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (94%)

Requests Now

66

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

peachbloom.com

peachbloom.com

653 ms

vkExUnit_style.css

vkExUnit_style.css

174 ms

header-top.css

header-top.css

343 ms

style.min.css

style.min.css

517 ms

style.css

style.css

343 ms

style.css

style.css

352 ms

style.css

style.css

356 ms

style.css

style.css

364 ms

style.css

style.css

512 ms

style.css

style.css

513 ms

style.css

style.css

527 ms

style.css

style.css

533 ms

style.css

style.css

545 ms

style.css

style.css

682 ms

style.css

style.css

683 ms

style.css

style.css

686 ms

swiper-bundle.min.css

swiper-bundle.min.css

704 ms

style.css

style.css

709 ms

style.css

style.css

725 ms

style.css

style.css

852 ms

style.css

style.css

853 ms

style.css

style.css

857 ms

style.css

style.css

880 ms

style.css

style.css

885 ms

style.css

style.css

906 ms

style.css

style.css

1022 ms

style.css

style.css

1022 ms

style.css

style.css

1029 ms

style.css

style.css

1056 ms

style.css

style.css

1087 ms

style.css

style.css

1193 ms

style.css

style.css

1200 ms

style.css

style.css

1232 ms

style.css

style.css

1238 ms

css2

css2

21 ms

css2

css2

37 ms

style.css

style.css

1201 ms

style.css

style.css

1033 ms

style.css

style.css

1048 ms

style.css

style.css

1067 ms

style.css

style.css

1094 ms

style.css

style.css

1030 ms

style.css

style.css

1030 ms

style.css

style.css

1068 ms

style.css

style.css

1071 ms

style.css

style.css

1279 ms

style.css

style.css

1032 ms

blog-card.css

blog-card.css

1033 ms

block-build.css

block-build.css

1052 ms

style.css

style.css

1066 ms

all.min.css

all.min.css

1249 ms

header-layout.css

header-layout.css

1159 ms

vk-campaign-text.css

vk-campaign-text.css

1034 ms

vk-mobile-fix-nav.css

vk-mobile-fix-nav.css

1056 ms

clipboard.min.js

clipboard.min.js

1091 ms

copy-button.js

copy-button.js

1147 ms

smooth-scroll.min.js

smooth-scroll.min.js

1171 ms

all.min.js

all.min.js

1150 ms

swiper-bundle.min.js

swiper-bundle.min.js

1062 ms

vk-slider.min.js

vk-slider.min.js

1117 ms

vk-accordion.min.js

vk-accordion.min.js

1111 ms

vk-faq2.min.js

vk-faq2.min.js

1129 ms

vk-animation.min.js

vk-animation.min.js

1163 ms

vk-tab.min.js

vk-tab.min.js

1138 ms

main.js

main.js

1064 ms

top_image_1.jpg

top_image_1.jpg

1042 ms

top_image_2.jpg

top_image_2.jpg

1423 ms

font

font

87 ms

font

font

5171 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

0 ms

Accessibility Review

peachbloom.com accessibility score

96

Accessibility Issues

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

Best Practices

peachbloom.com 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

Page has valid source maps

SEO Factors

peachbloom.com SEO score

83

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

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Peachbloom.com 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 Peachbloom.com 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

peachbloom.com

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