Tools & Wizards About Us
template-run.jp screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    28% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 97

    SEO

    Google-friendlier than
    92% of websites

template-run.jp

　無料ダウンロード！テンプレルン

Page Load Speed

5.7 sec in total

First Response

658 ms

Resources Loaded

4.1 sec

Page Rendered

878 ms

template-run.jp screenshot

About Website

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

無料で使えるテンプレートやイラストがダウンロード出来る雛形サイトです。年賀状素材や領収書や請求書などから駐車許可証、結婚証明書などのテンプレが無料ダウンロードが出来ますのでお気軽にご利用くださいませ。

Visit template-run.jp

Key Findings

We analyzed Template-run.jp page load time and found that the first response time was 658 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

template-run.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value19.4 s

0/100

10%

TBT (Total Blocking Time)

Value36,000 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value50.0 s

0/100

10%

Network Requests Diagram

template-run.jp

658 ms

template-run.jp

968 ms

js

76 ms

style.css

209 ms

common.css

374 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 82% of them (27 requests) were addressed to the original Template-run.jp, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Template-run.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 175.6 kB (66%)

Content Size

267.1 kB

After Optimization

91.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Template-run.jp main page is 267.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. 40% of websites need less resources to load. Javascripts take 175.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 32.4 kB

  • Original 39.1 kB
  • After minification 35.6 kB
  • After compression 6.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 32.4 kB or 83% of the original size.

JavaScript Optimization

-57%

Potential reduce by 99.7 kB

  • Original 175.0 kB
  • After minification 171.3 kB
  • After compression 75.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 99.7 kB or 57% of the original size.

CSS Optimization

-82%

Potential reduce by 43.4 kB

  • Original 53.0 kB
  • After minification 45.9 kB
  • After compression 9.6 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. Template-run.jp needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

31

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

template-run.jp

template-run.jp

658 ms

template-run.jp

template-run.jp

968 ms

js

js

76 ms

style.css

style.css

209 ms

common.css

common.css

374 ms

top.css

top.css

527 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

744 ms

jquery.floating-widget.min.js

jquery.floating-widget.min.js

560 ms

jquery.cookie.js

jquery.cookie.js

561 ms

jquery.accordion.js

jquery.accordion.js

548 ms

my_script.js

my_script.js

550 ms

ofi.min.js

ofi.min.js

674 ms

style.min.css

style.min.css

723 ms

styles.css

styles.css

1117 ms

frontend.css

frontend.css

1118 ms

adsbygoogle.js

adsbygoogle.js

81 ms

analytics.js

analytics.js

19 ms

collect

collect

14 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

214 ms

survey

survey

47 ms

001-01-01.png

001-01-01.png

377 ms

002-01-01.png

002-01-01.png

525 ms

003-01-01.png

003-01-01.png

560 ms

004-01-01.png

004-01-01.png

554 ms

005-01-01.png

005-01-01.png

1305 ms

006-01-01.png

006-01-01.png

1091 ms

007-01-01.png

007-01-01.png

551 ms

008-01-01.png

008-01-01.png

1031 ms

009-01-01.png

009-01-01.png

1072 ms

010-01-01.png

010-01-01.png

907 ms

011-01-01.png

011-01-01.png

730 ms

012-01-01-1.png

012-01-01-1.png

921 ms

1f4d1.svg

1f4d1.svg

42 ms

Accessibility Review

template-run.jp accessibility score

77

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.

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

template-run.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

template-run.jp SEO score

97

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Template-run.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 Template-run.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

template-run.jp

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