Tools & Wizards About Us
planex.co.jp screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

planex.co.jp

プラネックスコミュニケーションズ株式会社 PLANEX

Page Load Speed

8.3 sec in total

First Response

523 ms

Resources Loaded

7.5 sec

Page Rendered

212 ms

planex.co.jp screenshot

About Website

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

プラネックスコミュニケーションズ株式会社は無線LAN,ネットワークカメラ,ルータ,ハブ,プリントサーバーなどのネットワーク機器全般を取り扱いしています。無線LAN、ルータのことならプラネックス。

Visit planex.co.jp

Key Findings

We analyzed Planex.co.jp page load time and found that the first response time was 523 ms and then it took 7.7 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

planex.co.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value30.7 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.144

78/100

15%

TTI (Time to Interactive)

Value27.4 s

0/100

10%

Network Requests Diagram

planex.co.jp

523 ms

www.planex.co.jp

1380 ms

gtm.js

59 ms

base_02.css

679 ms

top_03.css

511 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 91% of them (83 requests) were addressed to the original Planex.co.jp, 3% (3 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Planex.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 262.9 kB (4%)

Content Size

6.9 MB

After Optimization

6.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Planex.co.jp main page is 6.9 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 6.6 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 73.9 kB

  • Original 82.8 kB
  • After minification 40.3 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 42.5 kB, which is 51% 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 73.9 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 76.1 kB

  • Original 6.6 MB
  • After minification 6.5 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. PLANEX images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 93.0 kB

  • Original 151.3 kB
  • After minification 135.2 kB
  • After compression 58.3 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 93.0 kB or 61% of the original size.

CSS Optimization

-86%

Potential reduce by 20.0 kB

  • Original 23.3 kB
  • After minification 14.8 kB
  • After compression 3.3 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. Planex.co.jp needs all CSS files to be minified and compressed as it can save up to 20.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (20%)

Requests Now

89

After Optimization

71

  • Images
  • JavaScript
  • CSS

The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PLANEX. 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 as a result speed up the page load time.

Network Requests Diagram

planex.co.jp

planex.co.jp

523 ms

www.planex.co.jp

www.planex.co.jp

1380 ms

gtm.js

gtm.js

59 ms

base_02.css

base_02.css

679 ms

top_03.css

top_03.css

511 ms

slideshow.css

slideshow.css

511 ms

jquery.js

jquery.js

1191 ms

jquery.easing.js

jquery.easing.js

527 ms

slideshow.js

slideshow.js

680 ms

smoothscroll.js

smoothscroll.js

679 ms

endless_scroll_min.js

endless_scroll_min.js

680 ms

jquery.zrssfeed.js

jquery.zrssfeed.js

193 ms

js

js

55 ms

background.png

background.png

513 ms

logo_comm.png

logo_comm.png

192 ms

search.jpg

search.jpg

189 ms

slideshow_bg.png

slideshow_bg.png

190 ms

load-indicator.gif

load-indicator.gif

188 ms

previous.png

previous.png

190 ms

next.png

next.png

509 ms

slideshow_mzk-ss04_02.jpg

slideshow_mzk-ss04_02.jpg

1700 ms

slideshow_cme-gl01-5_02.jpg

slideshow_cme-gl01-5_02.jpg

1571 ms

slideshow_fx2g-08em2.jpg

slideshow_fx2g-08em2.jpg

1361 ms

slideshow_inmg-bt60i.jpg

slideshow_inmg-bt60i.jpg

1577 ms

slideshow_cs-qs31-180.jpg

slideshow_cs-qs31-180.jpg

1860 ms

slideshow_cs-w80fhd2.jpg

slideshow_cs-w80fhd2.jpg

1536 ms

slideshow_cs-w50fhd2.jpg

slideshow_cs-w50fhd2.jpg

1872 ms

slideshow_usb-cam02_business.jpg

slideshow_usb-cam02_business.jpg

2390 ms

slideshow_gpe-2500-2t2.jpg

slideshow_gpe-2500-2t2.jpg

2420 ms

slideshow_articles_no13.gif

slideshow_articles_no13.gif

2278 ms

slideshow_usb-lan2500r2_usbc-lan2500r2_02.jpg

slideshow_usb-lan2500r2_usbc-lan2500r2_02.jpg

2209 ms

slideshow_mom-7s.jpg

slideshow_mom-7s.jpg

2873 ms

slideshow_fxg-05rpt2_02.jpg

slideshow_fxg-05rpt2_02.jpg

2722 ms

slideshow_articles_no0910.jpg

slideshow_articles_no0910.jpg

2891 ms

slideshow_ws-usb0304.jpg

slideshow_ws-usb0304.jpg

2979 ms

slideshow_cs-qs10pt.jpg

slideshow_cs-qs10pt.jpg

3414 ms

slideshow_mzk-dp300n.jpg

slideshow_mzk-dp300n.jpg

2930 ms

slideshow_cs-w90fhd2.jpg

slideshow_cs-w90fhd2.jpg

3402 ms

slideshow_cs-w72fhd2.jpg

slideshow_cs-w72fhd2.jpg

3886 ms

slideshow_articles_no08.jpg

slideshow_articles_no08.jpg

3401 ms

SpotCam-Ring.jpg

SpotCam-Ring.jpg

3610 ms

slideshow_fx2g-05em.jpg

slideshow_fx2g-05em.jpg

3680 ms

banner_MZK-SS04_campaign.jpg

banner_MZK-SS04_campaign.jpg

3571 ms

banner_CME-GL01-5_campaign.jpg

banner_CME-GL01-5_campaign.jpg

3573 ms

waku_240_bg_top_info.png

waku_240_bg_top_info.png

3585 ms

waku_240_bg.png

waku_240_bg.png

3741 ms

waku_240_bg_bottom.png

waku_240_bg_bottom.png

3742 ms

waku_240_bg_top_news.png

waku_240_bg_top_news.png

3756 ms

sdk.js

sdk.js

110 ms

waku_240_bg_top_support.png

waku_240_bg_top_support.png

3765 ms

js

js

99 ms

ga.js

ga.js

119 ms

sdk.js

sdk.js

22 ms

__utm.gif

__utm.gif

25 ms

41 ms

banner_articles.jpg

banner_articles.jpg

3671 ms

banner_Amazon_store.jpg

banner_Amazon_store.jpg

3726 ms

mzk-ss04.jpg

mzk-ss04.jpg

3726 ms

cme-gl01-5.jpg

cme-gl01-5.jpg

3740 ms

inmg-bt60i.jpg

inmg-bt60i.jpg

3761 ms

cs-qs31-180.jpg

cs-qs31-180.jpg

3527 ms

usb-cam02_02.jpg

usb-cam02_02.jpg

3546 ms

cs-qs10pt.jpg

cs-qs10pt.jpg

2723 ms

cs-qv40b_04.jpg

cs-qv40b_04.jpg

2549 ms

cs-qs51-lte.jpg

cs-qs51-lte.jpg

2529 ms

fx2g-08em2.jpg

fx2g-08em2.jpg

2546 ms

fx2g-05em.jpg

fx2g-05em.jpg

2511 ms

sf10g.jpg

sf10g.jpg

2367 ms

ws-usb03-thp_ws-usb04-pir.jpg

ws-usb03-thp_ws-usb04-pir.jpg

2384 ms

cs-w72fhd2.jpg

cs-w72fhd2.jpg

2045 ms

cs-w90fhd2.jpg

cs-w90fhd2.jpg

1994 ms

cs-w50fhd2.jpg

cs-w50fhd2.jpg

1903 ms

cs-w80fhd2.jpg

cs-w80fhd2.jpg

1964 ms

gpe-2500-2t2.jpg

gpe-2500-2t2.jpg

1672 ms

usb-lan2500r2.jpg

usb-lan2500r2.jpg

1552 ms

usbc-lan2500r2.jpg

usbc-lan2500r2.jpg

1535 ms

mzk-dp300n.jpg

mzk-dp300n.jpg

1512 ms

fxg-05rpt2.jpg

fxg-05rpt2.jpg

1483 ms

spotcam-ring.jpg

spotcam-ring.jpg

1159 ms

mom-7s.jpg

mom-7s.jpg

1161 ms

banner_HC-PRS01F_03.jpg

banner_HC-PRS01F_03.jpg

1179 ms

banner_HC-PRS02M_03.jpg

banner_HC-PRS02M_03.jpg

1023 ms

banner_cars.png

banner_cars.png

1209 ms

banner_collection.png

banner_collection.png

1045 ms

to_top.png

to_top.png

1124 ms

waku_690_bg_top_new_pro02.png

waku_690_bg_top_new_pro02.png

1051 ms

waku_690_bg.png

waku_690_bg.png

1023 ms

waku_690_bg_bottom.png

waku_690_bg_bottom.png

1022 ms

footer_bg.png

footer_bg.png

1044 ms

fotter_logo.png

fotter_logo.png

1121 ms

copyright.png

copyright.png

1054 ms

Accessibility Review

planex.co.jp accessibility score

67

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

planex.co.jp best practices score

58

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

SEO Factors

planex.co.jp SEO score

67

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Planex.co.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 Planex.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

planex.co.jp

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