Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

whitepercent.com

しろぱの買いたくない.com

Page Load Speed

5.9 sec in total

First Response

592 ms

Resources Loaded

4.9 sec

Page Rendered

384 ms

whitepercent.com screenshot

About Website

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

「こーすけらいてぃんぐ」代表のたかいこーすけのホームページです。Webライター初心者の方に向けて、参考になる情報を発信しています。筆者体験に基づく内容のみをコンテンツとしているため、その点は予めご了承ください。

Visit whitepercent.com

Key Findings

We analyzed Whitepercent.com page load time and found that the first response time was 592 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

whitepercent.com performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

whitepercent.com

592 ms

whitepercent.com

665 ms

www.kosuke-writing.com

1399 ms

swell-icons.css

338 ms

wpel.css

330 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Whitepercent.com, 88% (21 requests) were made to Kosuke-writing.com and 4% (1 request) were made to Fastly.picsum.photos. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Kosuke-writing.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.9 kB (20%)

Content Size

718.0 kB

After Optimization

575.0 kB

In fact, the total size of Whitepercent.com main page is 718.0 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. 20% of websites need less resources to load. Images take 493.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 135.9 kB

  • Original 172.9 kB
  • After minification 172.4 kB
  • After compression 37.0 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 135.9 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 29 B

  • Original 493.8 kB
  • After minification 493.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. Whitepercent images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 4.5 kB

  • Original 38.8 kB
  • After minification 38.8 kB
  • After compression 34.2 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 4.5 kB or 12% of the original size.

CSS Optimization

-20%

Potential reduce by 2.5 kB

  • Original 12.5 kB
  • After minification 12.3 kB
  • After compression 10.1 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. Whitepercent.com needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (65%)

Requests Now

20

After Optimization

7

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

Accessibility Review

whitepercent.com accessibility score

100

Accessibility Issues

Best Practices

whitepercent.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

whitepercent.com 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 Whitepercent.com 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 Whitepercent.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 data is detected on the main page of Whitepercent. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: