5.6 sec in total
532 ms
4.8 sec
258 ms
Welcome to templateking.jp homepage info - get ready to check Templateking best content for Japan right away, or after learning these important things about templateking.jp
完全無料・商用利用可のWordPressテンプレート配布サイト「テンプレートキング」。ファーストサーバ運営。
Visit templateking.jpWe analyzed Templateking.jp page load time and found that the first response time was 532 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
templateking.jp performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value6.1 s
12/100
25%
Value11.4 s
5/100
10%
Value40 ms
100/100
30%
Value0
100/100
15%
Value7.3 s
50/100
10%
532 ms
1117 ms
356 ms
358 ms
538 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 69% of them (66 requests) were addressed to the original Templateking.jp, 7% (7 requests) were made to Apis.google.com and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Templateking.jp.
Page size can be reduced by 402.6 kB (37%)
1.1 MB
690.3 kB
In fact, the total size of Templateking.jp main page is 1.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. 45% of websites need less resources to load. Images take 776.2 kB which makes up the majority of the site volume.
Potential reduce by 21.6 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 4.3 kB, which is 15% 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 21.6 kB or 75% of the original size.
Potential reduce by 185.3 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. Obviously, Templateking needs image optimization as it can save up to 185.3 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 165.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 165.6 kB or 66% of the original size.
Potential reduce by 30.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. Templateking.jp needs all CSS files to be minified and compressed as it can save up to 30.0 kB or 83% of the original size.
Number of requests can be reduced by 50 (53%)
94
44
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Templateking. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
templateking.jp
532 ms
www.templateking.jp
1117 ms
hookclass.js
356 ms
hascache.js
358 ms
global.css
538 ms
common.css
376 ms
index.css
377 ms
jquery1.8.3.pack.js
766 ms
library2.0.4.js
521 ms
common.js
526 ms
index.js
384 ms
platform.js
92 ms
gtm.js
72 ms
9fbDDIZJOoiEOhYfBXCvwQ1igvkT3F6aVkKE.gif
911 ms
mv_btn.png
188 ms
mv_img.png
1273 ms
mv_pop01.png
598 ms
mv_pop02.png
342 ms
bnr_zen.png
576 ms
newly_ttl.png
373 ms
fsv002wpbasicc01.jpg
710 ms
fsv002wpbasicc02.jpg
747 ms
fsv002wpbasicc03.jpg
599 ms
fsv002wpbasicc04.jpg
739 ms
fsv002wpbasicc05.jpg
768 ms
news_ttl.png
790 ms
update_ttl.png
872 ms
btn_search.png
917 ms
side_rank_ico01.png
931 ms
fsv002wpbasicc01.jpg
955 ms
side_rank_ico02.png
978 ms
fsv002wpbasicc05.jpg
1047 ms
side_rank_ico03.png
1094 ms
fsv002wpbasicc04.jpg
1303 ms
side_bnr02.png
1142 ms
side_bnr03.png
1356 ms
side_bnr01.png
1227 ms
side_bnr04.gif
1270 ms
footer_btn_old.png
1329 ms
footer_sns_ttl.png
1402 ms
footer_btn_pagetop.png
1442 ms
sdk.js
270 ms
header_logo_corporate.png
1433 ms
header_bnr.png
1473 ms
header_logo.png
1873 ms
header_gnavi01.png
1529 ms
header_gnavi02.png
1562 ms
widgets.js
4 ms
header_gnavi03.png
1578 ms
analytics.js
22 ms
fbevents.js
136 ms
linkid.js
11 ms
ec.js
21 ms
collect
11 ms
collect
50 ms
header_gnavi04.png
1474 ms
header_gnavi05.png
1516 ms
header_ico.png
1561 ms
109 ms
77 ms
xd_arbiter.php
231 ms
xd_arbiter.php
440 ms
header_bg_search.png
1424 ms
bnr_side.png
1436 ms
tag.js
68 ms
cb=gapi.loaded_0
28 ms
cb=gapi.loaded_1
58 ms
fastbutton
95 ms
mv_bg.jpg
1675 ms
tag
36 ms
postmessageRelay
50 ms
mv_txt.png
1482 ms
cb=gapi.loaded_0
26 ms
cb=gapi.loaded_1
29 ms
share_button.php
92 ms
templatelist_bg.png
1339 ms
ico_arrow01.png
1339 ms
api.js
29 ms
core:rpc:shindig.random:shindig.sha1.js
80 ms
2536007149-postmessagerelay.js
60 ms
vpc6VNjRPXV.js
481 ms
LVx-xkvaJ0b.png
542 ms
ico_accordion.png
1279 ms
ico_check_default.png
1348 ms
ico_check_color01.png
1380 ms
ico_check_color05.png
1351 ms
ico_check_color08.png
1378 ms
ico_check_color10.png
1372 ms
ico_check_color13.png
1355 ms
side_rank_bg.png
1363 ms
footer_bg.png
1360 ms
mv_btn_on.png
1366 ms
btn_search_on.png
1300 ms
footer_btn_old_on.png
1335 ms
ico_blank02.png
1315 ms
ya.js
361 ms
templateking.jp accessibility score
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
Links do not have a discernible name
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.
templateking.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
Page has valid source maps
templateking.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Templateking.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 Templateking.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.
templateking.jp
Open Graph data is detected on the main page of Templateking. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: