Tools & Wizards About Us
pnpk.net screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

pnpk.net

https://pnpk.net | 音楽とテクノロジー

Page Load Speed

8.8 sec in total

First Response

1.7 sec

Resources Loaded

6.7 sec

Page Rendered

313 ms

pnpk.net screenshot

About Website

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

主にギターにまつわる話が中心ですが、本職がWEBエンジニアというところもあり、その辺の話も書いています。 情シス、プログラマーを経験しています。laravelとreactの組み合わせが好きです。

Visit pnpk.net

Key Findings

We analyzed Pnpk.net page load time and found that the first response time was 1.7 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

pnpk.net performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

16/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value1,750 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

1739 ms

wp-emoji-release.min.js

867 ms

widget.css

349 ms

main_css.css

350 ms

css

25 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 61% of them (34 requests) were addressed to the original Pnpk.net, 11% (6 requests) were made to Pagead2.googlesyndication.com and 7% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Pnpk.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 451.5 kB (33%)

Content Size

1.4 MB

After Optimization

926.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pnpk.net 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. 40% of websites need less resources to load. Images take 710.1 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 50.4 kB

  • Original 70.0 kB
  • After minification 64.4 kB
  • After compression 19.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 50.4 kB or 72% of the original size.

Image Optimization

-3%

Potential reduce by 19.7 kB

  • Original 710.1 kB
  • After minification 690.3 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. Pnpk images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 234.5 kB

  • Original 416.5 kB
  • After minification 415.8 kB
  • After compression 182.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 234.5 kB or 56% of the original size.

CSS Optimization

-81%

Potential reduce by 146.8 kB

  • Original 181.1 kB
  • After minification 177.4 kB
  • After compression 34.2 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. Pnpk.net needs all CSS files to be minified and compressed as it can save up to 146.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (54%)

Requests Now

52

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1739 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

867 ms

widget.css

widget.css

349 ms

main_css.css

main_css.css

350 ms

css

css

25 ms

tc_common.min.css

tc_common.min.css

1433 ms

black2.min.css

black2.min.css

564 ms

style.css

style.css

324 ms

jquery.fancybox-1.3.4.min.css

jquery.fancybox-1.3.4.min.css

337 ms

styles_thumbnails.css.php

styles_thumbnails.css.php

567 ms

styles.css

styles.css

522 ms

jquery.js

jquery.js

1643 ms

jquery-migrate.min.js

jquery-migrate.min.js

874 ms

jquery.fancybox-1.3.4.min.js

jquery.fancybox-1.3.4.min.js

1096 ms

tc-scripts.min.js

tc-scripts.min.js

1531 ms

wp-autopager-0.5.1.min.js

wp-autopager-0.5.1.min.js

680 ms

tmkm-amazon.css

tmkm-amazon.css

854 ms

adsbygoogle.js

adsbygoogle.js

7 ms

related.css

related.css

521 ms

core.min.js

core.min.js

650 ms

modernizr.min.js

modernizr.min.js

881 ms

effect.min.js

effect.min.js

945 ms

retina.min.js

retina.min.js

823 ms

wp-embed.min.js

wp-embed.min.js

997 ms

analytics.js

analytics.js

18 ms

collect

collect

60 ms

pnpknet.png

pnpknet.png

395 ms

glyphicons-halflings.png

glyphicons-halflings.png

394 ms

ca-pub-6068931540434302.js

ca-pub-6068931540434302.js

252 ms

zrt_lookup.html

zrt_lookup.html

250 ms

show_ads_impl.js

show_ads_impl.js

190 ms

V86VyqXbc09Sss3BPsMj16CWcynf_cDxXwCLxiixG1c.ttf

V86VyqXbc09Sss3BPsMj16CWcynf_cDxXwCLxiixG1c.ttf

222 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

870 ms

rxxXUYj4oZ6Q5oDJFtEd6i3USBnSvpkopQaUR-2r7iU.ttf

rxxXUYj4oZ6Q5oDJFtEd6i3USBnSvpkopQaUR-2r7iU.ttf

231 ms

DSCF7632-570x350.jpg

DSCF7632-570x350.jpg

763 ms

DSCF7607.jpg

DSCF7607.jpg

906 ms

DSCF7356-570x350.jpg

DSCF7356-570x350.jpg

850 ms

DSCF7323-570x350.jpg

DSCF7323-570x350.jpg

922 ms

DSCF7303-570x350.jpg

DSCF7303-570x350.jpg

942 ms

IMG_0664-570x350.jpg

IMG_0664-570x350.jpg

1050 ms

DSCF6622.png

DSCF6622.png

2784 ms

DSCF6612-312x468-312x350.png

DSCF6612-312x468-312x350.png

2171 ms

IMG_0334-351x468-351x350.jpg

IMG_0334-351x468-351x350.jpg

1801 ms

ads

ads

288 ms

osd.js

osd.js

12 ms

ads

ads

215 ms

m_js_controller.js

m_js_controller.js

20 ms

abg.js

abg.js

40 ms

favicon

favicon

78 ms

favicon

favicon

96 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

63 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

52 ms

s

s

38 ms

x_button_blue2.png

x_button_blue2.png

12 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

12 ms

activeview

activeview

14 ms

Accessibility Review

pnpk.net accessibility score

86

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-*] attributes do not match their roles

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

Links do not have a discernible name

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

pnpk.net 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

SEO Factors

pnpk.net SEO score

91

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

pnpk.net

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