Tools & Wizards About Us
ploom.jp screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ploom.jp

CLUB JT

Page Load Speed

4.9 sec in total

First Response

510 ms

Resources Loaded

4.2 sec

Page Rendered

141 ms

ploom.jp screenshot

About Website

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

「プルーム・テック」は、バッテリーとカートリッジからなるたばこ用デバイスで、たばこ葉が詰まった専用たばこカプセルをセットすることでお楽しみいただけます。カートリッジ内のリキッドを霧化し、たばこカプセル内を通すことでたばこベイパーを発生させる独自テクノロジーを搭載しており、クリアなたばこの味わいを実現しました。

Visit ploom.jp

Key Findings

We analyzed Ploom.jp page load time and found that the first response time was 510 ms and then it took 4.4 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

ploom.jp performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value29.1 s

0/100

10%

Network Requests Diagram

ploom.jp

510 ms

adultauth

182 ms

fonts.css

206 ms

common.css

514 ms

authentication.css

472 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 50% of them (7 requests) were addressed to the original Ploom.jp, 21% (3 requests) were made to Google-analytics.com and 7% (1 request) were made to Cloud.typography.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Ploom.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 319.3 kB (72%)

Content Size

442.1 kB

After Optimization

122.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Ploom.jp main page is 442.1 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. Only 10% of websites need less resources to load. Javascripts take 383.5 kB which makes up the majority of the site volume.

HTML Optimization

-50%

Potential reduce by 1.4 kB

  • Original 2.7 kB
  • After minification 2.7 kB
  • After compression 1.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 1.4 kB or 50% of the original size.

JavaScript Optimization

-70%

Potential reduce by 268.9 kB

  • Original 383.5 kB
  • After minification 328.7 kB
  • After compression 114.6 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 268.9 kB or 70% of the original size.

CSS Optimization

-88%

Potential reduce by 49.1 kB

  • Original 55.9 kB
  • After minification 36.8 kB
  • After compression 6.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. Ploom.jp needs all CSS files to be minified and compressed as it can save up to 49.1 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (27%)

Requests Now

11

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ploom.jp

ploom.jp

510 ms

adultauth

adultauth

182 ms

fonts.css

fonts.css

206 ms

common.css

common.css

514 ms

authentication.css

authentication.css

472 ms

common.js

common.js

2363 ms

css

css

62 ms

gtm.js

gtm.js

108 ms

authentication_txt_note.gif

authentication_txt_note.gif

176 ms

authentication_txt_copyright.gif

authentication_txt_copyright.gif

162 ms

analytics.js

analytics.js

56 ms

linkid.js

linkid.js

16 ms

collect

collect

10 ms

collect

collect

64 ms

Accessibility Review

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

ploom.jp best practices score

83

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

Browser errors were logged to the console

SEO Factors

ploom.jp SEO score

86

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

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

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

ploom.jp

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