Tools & Wizards About Us
perfume-web.jp screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

perfume-web.jp

Perfume Official Site

Page Load Speed

11.4 sec in total

First Response

353 ms

Resources Loaded

9.8 sec

Page Rendered

1.3 sec

perfume-web.jp screenshot

About Website

Visit perfume-web.jp now to see the best up-to-date Perfume Web content for Japan and also check out these interesting facts you probably never knew about perfume-web.jp

所属事務所アミューズによるPerfumeオフィシャルサイト

Visit perfume-web.jp

Key Findings

We analyzed Perfume-web.jp page load time and found that the first response time was 353 ms and then it took 11.1 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

perfume-web.jp performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value4,420 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.121

1/100

15%

TTI (Time to Interactive)

Value33.6 s

0/100

10%

Network Requests Diagram

perfume-web.jp

353 ms

www.perfume-web.jp

1004 ms

gtm.js

114 ms

yrv0iiq.css

629 ms

style.css

1003 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 77% of them (83 requests) were addressed to the original Perfume-web.jp, 4% (4 requests) were made to Googletagmanager.com and 4% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Perfume-web.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (18%)

Content Size

11.5 MB

After Optimization

9.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 29.1 kB

  • Original 35.7 kB
  • After minification 32.8 kB
  • After compression 6.6 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 29.1 kB or 81% of the original size.

Image Optimization

-18%

Potential reduce by 2.1 MB

  • Original 11.4 MB
  • After minification 9.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. Obviously, Perfume Web needs image optimization as it can save up to 2.1 MB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 1.5 kB

  • Original 58.5 kB
  • After minification 58.2 kB
  • After compression 57.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 2.1 kB

  • Original 24.7 kB
  • After minification 24.7 kB
  • After compression 22.6 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. Perfume-web.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (32%)

Requests Now

104

After Optimization

71

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

perfume-web.jp

perfume-web.jp

353 ms

www.perfume-web.jp

www.perfume-web.jp

1004 ms

gtm.js

gtm.js

114 ms

yrv0iiq.css

yrv0iiq.css

629 ms

style.css

style.css

1003 ms

common.css

common.css

720 ms

all.css

all.css

70 ms

slick.css

slick.css

55 ms

trans.js

trans.js

60 ms

jquery.min.js

jquery.min.js

58 ms

slick.min.js

slick.min.js

57 ms

main.js

main.js

875 ms

js

js

50 ms

analytics.js

analytics.js

15 ms

collect

collect

199 ms

collect

collect

201 ms

destination

destination

186 ms

collect

collect

27 ms

collect

collect

17 ms

ga-audiences

ga-audiences

169 ms

ga-audiences

ga-audiences

229 ms

p.css

p.css

32 ms

flq3bub.js

flq3bub.js

148 ms

p.gif

p.gif

3 ms

logo_white.svg

logo_white.svg

667 ms

logo@2x.png

logo@2x.png

672 ms

logo_white@2x.png

logo_white@2x.png

289 ms

line_black.png

line_black.png

290 ms

twitter_black@2x.png

twitter_black@2x.png

290 ms

youtube_black@2x.png

youtube_black@2x.png

608 ms

facebook_black@2x.png

facebook_black@2x.png

836 ms

instagram_black@2x.png

instagram_black@2x.png

935 ms

tiktok_black@2x.png

tiktok_black@2x.png

954 ms

other_black@2x.png

other_black@2x.png

777 ms

profile_download.jpg

profile_download.jpg

1825 ms

download_logo1@2x.png

download_logo1@2x.png

839 ms

download_logo2@2x.png

download_logo2@2x.png

947 ms

download_logo3@2x.png

download_logo3@2x.png

1334 ms

download_logo4@2x.png

download_logo4@2x.png

1506 ms

download_logo5@2x.png

download_logo5@2x.png

1107 ms

download_logo6@2x.png

download_logo6@2x.png

1613 ms

download_logo7@2x.png

download_logo7@2x.png

1125 ms

download_logo8@2x.png

download_logo8@2x.png

1280 ms

download_logo9@2x.png

download_logo9@2x.png

1807 ms

download_logo10@2x.png

download_logo10@2x.png

1947 ms

download_logo11@2x.png

download_logo11@2x.png

1997 ms

download_logo12@2x.png

download_logo12@2x.png

2175 ms

download_logo13@2x.png

download_logo13@2x.png

1951 ms

download_logo14@2x.png

download_logo14@2x.png

1979 ms

mainvisual_pc202307.jpg

mainvisual_pc202307.jpg

2985 ms

mainvisual_sp202307.jpg

mainvisual_sp202307.jpg

3275 ms

background@2x.jpg

background@2x.jpg

2791 ms

image.php

image.php

2842 ms

image.php

image.php

3686 ms

image.php

image.php

3378 ms

image.php

image.php

3672 ms

image.php

image.php

3564 ms

image.php

image.php

4009 ms

image.php

image.php

3973 ms

config

config

915 ms

image.php

image.php

4154 ms

TF986KXW28PXWQ4NGYVL

TF986KXW28PXWQ4NGYVL

41 ms

js

js

72 ms

d

d

45 ms

d

d

38 ms

image.php

image.php

4151 ms

image.php

image.php

4260 ms

image.php

image.php

4752 ms

arrow_small@2x.png

arrow_small@2x.png

3539 ms

all@2x.png

all@2x.png

3847 ms

all_white@2x.png

all_white@2x.png

4144 ms

image.php

image.php

3652 ms

image.php

image.php

4776 ms

image.php

image.php

3798 ms

image.php

image.php

3776 ms

image.php

image.php

4491 ms

logo_pta@2x.png

logo_pta@2x.png

4353 ms

main.js

main.js

4 ms

logo_pta_name@2x.png

logo_pta_name@2x.png

4270 ms

bnr_pta_01@2x.jpg

bnr_pta_01@2x.jpg

4023 ms

bnr_pta_01_sp@2x.jpg

bnr_pta_01_sp@2x.jpg

3936 ms

bnr_pta_02@2x.jpg

bnr_pta_02@2x.jpg

4975 ms

bnr_pta_02_sp@2x.jpg

bnr_pta_02_sp@2x.jpg

4050 ms

bnr_pta_03@2x.jpg

bnr_pta_03@2x.jpg

4190 ms

bnr_pta_03_sp@2x.jpg

bnr_pta_03_sp@2x.jpg

4730 ms

logo_asmart@2x.png

logo_asmart@2x.png

3788 ms

logo_poc@2x.png

logo_poc@2x.png

3781 ms

footer_logo1@2x.png

footer_logo1@2x.png

3835 ms

footer_logo2@2x.png

footer_logo2@2x.png

4298 ms

footer_logo3@2x.png

footer_logo3@2x.png

4398 ms

footer_logo4@2x.png

footer_logo4@2x.png

4280 ms

footer_logo5@2x.png

footer_logo5@2x.png

3182 ms

footer_logo6@2x.png

footer_logo6@2x.png

3302 ms

footer_logo7@2x.png

footer_logo7@2x.png

3820 ms

footer_logo8@2x.png

footer_logo8@2x.png

3669 ms

footer_logo9@2x.png

footer_logo9@2x.png

3097 ms

footer_logo10@2x.png

footer_logo10@2x.png

3493 ms

footer_logo11@2x.png

footer_logo11@2x.png

3456 ms

footer_logo12@2x.png

footer_logo12@2x.png

2958 ms

footer_logo13@2x.png

footer_logo13@2x.png

2728 ms

footer_logo14@2x.png

footer_logo14@2x.png

3300 ms

line.png

line.png

3223 ms

twitter@2x.png

twitter@2x.png

2743 ms

youtube@2x.png

youtube@2x.png

2685 ms

facebook@2x.png

facebook@2x.png

2712 ms

instagram@2x.png

instagram@2x.png

2717 ms

tiktok@2x.png

tiktok@2x.png

2738 ms

other@2x.png

other@2x.png

2662 ms

Accessibility Review

perfume-web.jp accessibility score

80

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

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.

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

perfume-web.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

SEO Factors

perfume-web.jp SEO score

90

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

perfume-web.jp

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