Tools & Wizards About Us
preno.jp screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

preno.jp

国内でも徹底検品！安全・安心で高品質のオリジナル・ぬいぐるみ製作サイト | プレノ

Page Load Speed

3.9 sec in total

First Response

507 ms

Resources Loaded

3.1 sec

Page Rendered

310 ms

preno.jp screenshot

About Website

Welcome to preno.jp homepage info - get ready to check Preno best content right away, or after learning these important things about preno.jp

どこよりも高品質なぬいぐるみを徹底した検品でお届け！小ロットもOK。テディベア、ノベルティ、ウェディングにも最適。ぬいぐるみ修理や販売も行っています。

Visit preno.jp

Key Findings

We analyzed Preno.jp page load time and found that the first response time was 507 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

preno.jp performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.415

23/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

preno.jp

507 ms

preno.jp

770 ms

reset.css

188 ms

common.css

375 ms

js

72 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 97% of them (38 requests) were addressed to the original Preno.jp, 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Preno.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 18.4 kB (9%)

Content Size

206.4 kB

After Optimization

188.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Preno.jp main page is 206.4 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 153.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 11.5 kB

  • Original 15.3 kB
  • After minification 12.4 kB
  • After compression 3.8 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 2.9 kB, which is 19% 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 11.5 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 6.1 kB

  • Original 153.5 kB
  • After minification 147.4 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. Preno images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 132 B

  • Original 33.2 kB
  • After minification 33.2 kB
  • After compression 33.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. This website has mostly compressed JavaScripts.

CSS Optimization

-17%

Potential reduce by 751 B

  • Original 4.5 kB
  • After minification 4.5 kB
  • After compression 3.7 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. Preno.jp needs all CSS files to be minified and compressed as it can save up to 751 B or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (11%)

Requests Now

37

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

preno.jp

preno.jp

507 ms

preno.jp

preno.jp

770 ms

reset.css

reset.css

188 ms

common.css

common.css

375 ms

js

js

72 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

702 ms

jquery.easing.min.js

jquery.easing.min.js

527 ms

lazyload.min.js

lazyload.min.js

528 ms

common.js

common.js

549 ms

header_logo.png

header_logo.png

188 ms

btn_aboutus.png

btn_aboutus.png

408 ms

btn_products.png

btn_products.png

336 ms

gmenu_howtoorder.png

gmenu_howtoorder.png

335 ms

gmenu_price.png

gmenu_price.png

354 ms

gmenu_examples.png

gmenu_examples.png

374 ms

gmenu_faq.png

gmenu_faq.png

498 ms

btn_contact.png

btn_contact.png

500 ms

menu_open.png

menu_open.png

502 ms

mainvisual1.webp

mainvisual1.webp

1447 ms

mainvisual1_sp_pre.png

mainvisual1_sp_pre.png

561 ms

mainvisual2_pre.png

mainvisual2_pre.png

595 ms

mainvisual2_title.webp

mainvisual2_title.webp

672 ms

mainvisual2_bg.png

mainvisual2_bg.png

677 ms

icon_list_footprint_pink.png

icon_list_footprint_pink.png

678 ms

mainvisual3_title.webp

mainvisual3_title.webp

747 ms

mainvisual3_bg.png

mainvisual3_bg.png

783 ms

icon_list_footprint_green.png

icon_list_footprint_green.png

847 ms

header_examples.png

header_examples.png

851 ms

header_examples_sp.png

header_examples_sp.png

854 ms

examples_pre.png

examples_pre.png

934 ms

icon_btn.png

icon_btn.png

970 ms

banner_teddy_bear.webp

banner_teddy_bear.webp

1021 ms

banner_teddy_bear_sp.webp

banner_teddy_bear_sp.webp

1375 ms

banner_blog.png

banner_blog.png

1204 ms

banner_facebook.jpg

banner_facebook.jpg

1120 ms

banner_preno_novelty.webp

banner_preno_novelty.webp

1159 ms

footer_top.png

footer_top.png

1195 ms

btn_facebook.png

btn_facebook.png

1307 ms

btn_pagetop.png

btn_pagetop.png

1346 ms

Accessibility Review

preno.jp accessibility score

94

Accessibility Issues

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.

Best Practices

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

preno.jp 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 Preno.jp 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 Preno.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

preno.jp

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