Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

peekan.com

ピーカン!アウトドア・釣り・旅行情報 | キャンプレポート、釣果報告、初心者釣り講座、管理釣り場紹介など

Page Load Speed

11.6 sec in total

First Response

1.5 sec

Resources Loaded

9.6 sec

Page Rendered

479 ms

peekan.com screenshot

About Website

Click here to check amazing Peekan content for Japan. Otherwise, check out these important facts you probably never knew about peekan.com

キャンプレポート、釣果報告、初心者釣り講座、管理釣り場紹介など

Visit peekan.com

Key Findings

We analyzed Peekan.com page load time and found that the first response time was 1.5 sec and then it took 10.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

peekan.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value0.9 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

peekan.com

1540 ms

wp-emoji-release.min.js

841 ms

jquery.js

1217 ms

jquery-migrate.min.js

528 ms

style.css

738 ms

Our browser made a total of 165 requests to load all elements on the main page. We found that 50% of them (83 requests) were addressed to the original Peekan.com, 14% (23 requests) were made to Static.xx.fbcdn.net and 8% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Peekan.com.

Page Optimization Overview & Recommendations

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

Content Size

4.1 MB

After Optimization

2.0 MB

In fact, the total size of Peekan.com main page is 4.1 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. 65% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 55.5 kB

  • Original 69.1 kB
  • After minification 66.1 kB
  • After compression 13.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 55.5 kB or 80% of the original size.

Image Optimization

-46%

Potential reduce by 1.5 MB

  • Original 3.3 MB
  • After minification 1.8 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, Peekan needs image optimization as it can save up to 1.5 MB or 46% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-61%

Potential reduce by 379.9 kB

  • Original 619.8 kB
  • After minification 618.7 kB
  • After compression 239.9 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 379.9 kB or 61% of the original size.

CSS Optimization

-89%

Potential reduce by 166.5 kB

  • Original 187.5 kB
  • After minification 172.9 kB
  • After compression 21.0 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. Peekan.com needs all CSS files to be minified and compressed as it can save up to 166.5 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 77 (48%)

Requests Now

161

After Optimization

84

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

Accessibility Review

peekan.com accessibility score

84

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

peekan.com 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

SEO Factors

peekan.com SEO score

55

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Peekan.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Peekan.com 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

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