5.1 sec in total
533 ms
4.1 sec
461 ms
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.jpWe analyzed Template-run.jp page load time and found that the first response time was 533 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
template-run.jp performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value4.5 s
37/100
25%
Value10.6 s
7/100
10%
Value2,030 ms
7/100
30%
Value0
100/100
15%
Value12.0 s
16/100
10%
533 ms
1035 ms
61 ms
197 ms
352 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 40% of them (27 requests) were addressed to the original Template-run.jp, 12% (8 requests) were made to Googleads.g.doubleclick.net and 12% (8 requests) were made to Tpc.googlesyndication.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 size can be reduced by 562.8 kB (18%)
3.1 MB
2.5 MB
In fact, the total size of Template-run.jp main page is 3.1 MB. 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. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 52.1 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 52.1 kB or 80% of the original size.
Potential reduce by 163.7 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. Template Run images are well optimized though.
Potential reduce by 341.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 341.6 kB or 39% of the original size.
Potential reduce by 5.3 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 5.3 kB or 26% of the original size.
Number of requests can be reduced by 30 (51%)
59
29
The browser has sent 59 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 23 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
template-run.jp
533 ms
template-run.jp
1035 ms
js
61 ms
style.css
197 ms
common.css
352 ms
top.css
515 ms
jquery-1.9.1.min.js
687 ms
jquery.floating-widget.min.js
514 ms
jquery.cookie.js
517 ms
jquery.accordion.js
526 ms
my_script.js
542 ms
ofi.min.js
685 ms
style.min.css
686 ms
styles.css
760 ms
frontend.css
760 ms
adsbygoogle.js
89 ms
js
48 ms
analytics.js
18 ms
collect
48 ms
wp-emoji-release.min.js
224 ms
show_ads_impl.js
114 ms
survey
70 ms
001-01200.png
182 ms
001-01169.png
344 ms
001-01-01-1.jpg
523 ms
015-00.jpg
342 ms
010-01-012.png
174 ms
001-01140.png
407 ms
001-01111.png
346 ms
001-00-4.png
546 ms
007-00.jpg
1101 ms
5c2a3785880f031aeab5c06344ac1dd5.jpg
1318 ms
026-02-1.jpg
1068 ms
025-02-1.jpg
1122 ms
ads
758 ms
1f4d1.svg
25 ms
2764.svg
25 ms
ads
684 ms
reactive_library.js
70 ms
ads
777 ms
ads
487 ms
ads
388 ms
zrt_lookup.html
69 ms
css2
94 ms
load_preloaded_resource.js
83 ms
abg_lite.js
86 ms
s
66 ms
window_focus.js
94 ms
qs_click_protection.js
97 ms
ufs_web_display.js
82 ms
292c8da9ba2bf735c15092bbb96159c9.js
76 ms
fullscreen_api_adapter.js
247 ms
interstitial_ad_frame.js
247 ms
one_click_handler_one_afma.js
245 ms
icon.png
50 ms
3066195693165634573
244 ms
feedback_grey600_24dp.png
59 ms
settings_grey600_24dp.png
70 ms
css
103 ms
css
103 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
45 ms
KFOmCnqEu92Fr1Me5Q.ttf
52 ms
activeview
118 ms
7oEUkR-0Uy9FIahscmU7Lq7lgP_YvsNEVpm_VpMj8bQ.js
18 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
92 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
16 ms
font
97 ms
template-run.jp accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
template-run.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
template-run.jp SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
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.
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: