Tools & Wizards About Us
plimo.jp screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

plimo.jp

渋谷区のplimo

Page Load Speed

5 sec in total

First Response

504 ms

Resources Loaded

4.1 sec

Page Rendered

351 ms

plimo.jp screenshot

About Website

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

plimoはレスポンシブデザインを採用したWebサイト制作です。 スマートフォンの大幅な普及とタブレットをはじめとしたデバイスの多様化に合わせた、1ソースで管理しデザインの画面サイズに応じて自動的にデザイン・レイアウトを最適化したWebサイトになります。

Visit plimo.jp

Key Findings

We analyzed Plimo.jp page load time and found that the first response time was 504 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 70% of websites can load faster.

Performance Metrics

plimo.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value11.1 s

5/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.357

30/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

plimo.jp

504 ms

www.plimo.jp

524 ms

static_common.min.css

475 ms

touchTouch.css

323 ms

plimo_structure_5.css

383 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 50% of them (30 requests) were addressed to the original Plimo.jp, 33% (20 requests) were made to Static.plimo.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Plimo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 324.3 kB (23%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 13.6 kB

  • Original 18.2 kB
  • After minification 16.2 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 1.9 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 13.6 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 32.2 kB

  • Original 1.0 MB
  • After minification 968.7 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. Plimo images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 167.3 kB

  • Original 247.3 kB
  • After minification 209.9 kB
  • After compression 80.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 167.3 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 111.2 kB

  • Original 130.0 kB
  • After minification 79.4 kB
  • After compression 18.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. Plimo.jp needs all CSS files to be minified and compressed as it can save up to 111.2 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

58

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

plimo.jp

plimo.jp

504 ms

www.plimo.jp

www.plimo.jp

524 ms

static_common.min.css

static_common.min.css

475 ms

touchTouch.css

touchTouch.css

323 ms

plimo_structure_5.css

plimo_structure_5.css

383 ms

plimo_content_5.css

plimo_content_5.css

652 ms

camera.css

camera.css

319 ms

typesquare.js

typesquare.js

411 ms

jquery.min.js

jquery.min.js

785 ms

static_type_noscript_image_replace.js

static_type_noscript_image_replace.js

320 ms

base.js

base.js

318 ms

touchTouch.jquery.js

touchTouch.jquery.js

470 ms

jquery-migrate-1.1.1.js

jquery-migrate-1.1.1.js

472 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

471 ms

script.js

script.js

472 ms

superfish.js

superfish.js

624 ms

jquery.ui.totop.js

jquery.ui.totop.js

627 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

627 ms

camera.js

camera.js

1097 ms

jquery.equalheights.js

jquery.equalheights.js

627 ms

jquery.mobile.customized.min.js

jquery.mobile.customized.min.js

937 ms

plimo.js

plimo.js

372 ms

js

js

23 ms

reset.css

reset.css

413 ms

skeleton.css

skeleton.css

411 ms

font-awesome.css

font-awesome.css

567 ms

superfish.css

superfish.css

561 ms

css

css

26 ms

css

css

37 ms

css

css

45 ms

logo.png

logo.png

211 ms

genom_news.html

genom_news.html

982 ms

chara_plimo01.png

chara_plimo01.png

706 ms

img_main.jpg

img_main.jpg

951 ms

img_sp_main.jpg

img_sp_main.jpg

528 ms

header_bnr.png

header_bnr.png

480 ms

bg01.png

bg01.png

350 ms

h2a.png

h2a.png

358 ms

img_top01.jpg

img_top01.jpg

548 ms

img_top02.jpg

img_top02.jpg

681 ms

img_top03.jpg

img_top03.jpg

710 ms

img_top04.jpg

img_top04.jpg

665 ms

bg02.jpg

bg02.jpg

806 ms

icon01.png

icon01.png

787 ms

icon02.png

icon02.png

861 ms

icon03.png

icon03.png

873 ms

icon04.png

icon04.png

964 ms

bg03.jpg

bg03.jpg

1170 ms

img_top05.png

img_top05.png

1218 ms

img_top06.png

img_top06.png

1370 ms

img_top07.png

img_top07.png

1422 ms

img_top08.png

img_top08.png

1129 ms

bg04.jpg

bg04.jpg

2106 ms

graph.png

graph.png

1290 ms

fbn02.png

fbn02.png

1306 ms

fbn01.png

fbn01.png

1352 ms

analytics.js

analytics.js

21 ms

totop.png

totop.png

1339 ms

collect

collect

11 ms

collect

collect

58 ms

Accessibility Review

plimo.jp accessibility score

71

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.

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

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

plimo.jp best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

plimo.jp SEO score

100

Search Engine Optimization Advices

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

plimo.jp

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