Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

wiki.poyo.jp

FrontPage - よくきたWiki

Page Load Speed

9.6 sec in total

First Response

2.9 sec

Resources Loaded

6.5 sec

Page Rendered

225 ms

wiki.poyo.jp screenshot

About Website

Welcome to wiki.poyo.jp homepage info - get ready to check Wiki Poyo best content for New Zealand right away, or after learning these important things about wiki.poyo.jp

PHPやLinuxなどのオープンソース関係をはじめ、興味があるものをとことんメモしていきます

Visit wiki.poyo.jp

Key Findings

We analyzed Wiki.poyo.jp page load time and found that the first response time was 2.9 sec and then it took 6.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

wiki.poyo.jp performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

79/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,720 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

wiki.poyo.jp

2933 ms

yokukita.ja.css

427 ms

pleasewait.gif

254 ms

append.gif

354 ms

yokukita_wiki.gif

359 ms

Our browser made a total of 138 requests to load all elements on the main page. We found that 17% of them (24 requests) were addressed to the original Wiki.poyo.jp, 9% (12 requests) were made to B.hatena.ne.jp and 7% (9 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Wiki.poyo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 301.7 kB (60%)

Content Size

501.2 kB

After Optimization

199.5 kB

In fact, the total size of Wiki.poyo.jp main page is 501.2 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. 50% of websites need less resources to load. Javascripts take 348.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 29.4 kB

  • Original 37.1 kB
  • After minification 36.7 kB
  • After compression 7.7 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 29.4 kB or 79% of the original size.

Image Optimization

-9%

Potential reduce by 4.5 kB

  • Original 49.3 kB
  • After minification 44.8 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. Wiki Poyo images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 214.2 kB

  • Original 348.9 kB
  • After minification 343.0 kB
  • After compression 134.8 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 214.2 kB or 61% of the original size.

CSS Optimization

-81%

Potential reduce by 53.7 kB

  • Original 65.9 kB
  • After minification 50.8 kB
  • After compression 12.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. Wiki.poyo.jp needs all CSS files to be minified and compressed as it can save up to 53.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (61%)

Requests Now

132

After Optimization

51

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

Accessibility Review

wiki.poyo.jp accessibility score

62

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

wiki.poyo.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

wiki.poyo.jp SEO score

58

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

    EN

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wiki.poyo.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Wiki.poyo.jp main page’s claimed encoding is euc-jp. 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

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