Tools & Wizards About Us
presnt.jp screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

presnt.jp

presnt.jp

Page Load Speed

2.8 sec in total

First Response

533 ms

Resources Loaded

2 sec

Page Rendered

314 ms

presnt.jp screenshot

About Website

Welcome to presnt.jp homepage info - get ready to check Presnt best content for Japan right away, or after learning these important things about presnt.jp

企業のブランディング戦略から構築、広告コミュニケーションに対し、継続的な対話と本質の発見、その定着までをご提供する、フリーランスのブランディングとデザインのブティックです

Visit presnt.jp

Key Findings

We analyzed Presnt.jp page load time and found that the first response time was 533 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

presnt.jp performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.697

7/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

presnt.jp

533 ms

css

23 ms

css

35 ms

bundle.css

165 ms

typesquare.js

228 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 57% of them (16 requests) were addressed to the original Presnt.jp, 14% (4 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Presnt.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 161.1 kB (30%)

Content Size

543.1 kB

After Optimization

382.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Presnt.jp main page is 543.1 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. 25% of websites need less resources to load. Images take 302.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 13.5 kB

  • Original 16.4 kB
  • After minification 12.5 kB
  • After compression 2.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 3.9 kB, which is 24% 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 13.5 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 3.7 kB

  • Original 302.3 kB
  • After minification 298.6 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. Presnt images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 131.2 kB

  • Original 208.8 kB
  • After minification 208.8 kB
  • After compression 77.6 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 131.2 kB or 63% of the original size.

CSS Optimization

-81%

Potential reduce by 12.6 kB

  • Original 15.5 kB
  • After minification 15.5 kB
  • After compression 3.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. Presnt.jp needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (35%)

Requests Now

20

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

presnt.jp

presnt.jp

533 ms

css

css

23 ms

css

css

35 ms

bundle.css

bundle.css

165 ms

typesquare.js

typesquare.js

228 ms

bundle.js

bundle.js

621 ms

logo.png

logo.png

314 ms

number_1.png

number_1.png

311 ms

thumb_1.png

thumb_1.png

784 ms

number_2.png

number_2.png

329 ms

thumb_2.png

thumb_2.png

692 ms

number_3.png

number_3.png

472 ms

thumb_3.png

thumb_3.png

474 ms

number_4.png

number_4.png

497 ms

thumb_4.png

thumb_4.png

941 ms

number_5.png

number_5.png

691 ms

thumb_5.png

thumb_5.png

691 ms

number_6.png

number_6.png

776 ms

thumb_6.png

thumb_6.png

1409 ms

ga.js

ga.js

10 ms

__utm.gif

__utm.gif

26 ms

mPjsOObnC77fp1cvZlOfIfn8qdNnd5eCmWXua5W-n7c.woff

mPjsOObnC77fp1cvZlOfIfn8qdNnd5eCmWXua5W-n7c.woff

7 ms

Zd2E9abXLFGSr9G3YK2MsFzqCfRpIA3W6ypxnPISCPA.woff

Zd2E9abXLFGSr9G3YK2MsFzqCfRpIA3W6ypxnPISCPA.woff

21 ms

b9QBgL0iMZfDSpmcXcE8nNeiznanRB67rGZDYkMvKPc.woff

b9QBgL0iMZfDSpmcXcE8nNeiznanRB67rGZDYkMvKPc.woff

21 ms

b9QBgL0iMZfDSpmcXcE8nCSLrGe-fkSRw2DeVgOoWcQ.woff

b9QBgL0iMZfDSpmcXcE8nCSLrGe-fkSRw2DeVgOoWcQ.woff

22 ms

collect

collect

62 ms

200 ms

ab.woff

ab.woff

8 ms

Accessibility Review

presnt.jp accessibility score

73

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

presnt.jp 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

presnt.jp SEO score

94

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Presnt.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Presnt.jp 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

presnt.jp

Open Graph data is detected on the main page of Presnt. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: