Tools & Wizards About Us
templatemonster.jp screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

templatemonster.jp

テンプレートモンスター ジャパン サービス終了のお知らせ

Page Load Speed

10.3 sec in total

First Response

518 ms

Resources Loaded

9.5 sec

Page Rendered

286 ms

templatemonster.jp screenshot

About Website

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

平素はテンプレートモンスター ジャパンをご利用頂きましてありがとうございます。 2020年7月31日をもって、

Visit templatemonster.jp

Key Findings

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

Performance Metrics

templatemonster.jp performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

templatemonster.jp

518 ms

www.templatemonster.jp

1425 ms

tmjcss.css

889 ms

showtrail.css

350 ms

top.js

522 ms

Our browser made a total of 146 requests to load all elements on the main page. We found that 65% of them (95 requests) were addressed to the original Templatemonster.jp, 5% (7 requests) were made to Apis.google.com and 3% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Templatemonster.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 329.5 kB (37%)

Content Size

900.6 kB

After Optimization

571.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 61.1 kB

  • Original 75.6 kB
  • After minification 73.9 kB
  • After compression 14.5 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 61.1 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 18.4 kB

  • Original 449.6 kB
  • After minification 431.2 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. Templatemonster images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 193.5 kB

  • Original 309.0 kB
  • After minification 279.5 kB
  • After compression 115.4 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 193.5 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 56.4 kB

  • Original 66.5 kB
  • After minification 50.2 kB
  • After compression 10.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. Templatemonster.jp needs all CSS files to be minified and compressed as it can save up to 56.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 71 (52%)

Requests Now

137

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

templatemonster.jp

templatemonster.jp

518 ms

www.templatemonster.jp

www.templatemonster.jp

1425 ms

tmjcss.css

tmjcss.css

889 ms

showtrail.css

showtrail.css

350 ms

top.js

top.js

522 ms

preview_templates.js

preview_templates.js

367 ms

loader.js

loader.js

369 ms

swfobject_modified.js

swfobject_modified.js

716 ms

plusone.js

plusone.js

88 ms

share.js

share.js

9 ms

bookmark_button.js

bookmark_button.js

341 ms

widgets.js

widgets.js

5 ms

noteit.js

noteit.js

18 ms

index.js

index.js

363 ms

conversion.js

conversion.js

14 ms

s_retargeting.js

s_retargeting.js

544 ms

conversion.js

conversion.js

911 ms

clickheat.js

clickheat.js

568 ms

jquery-1.3.min.js

jquery-1.3.min.js

910 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

27 ms

button-only.gif

button-only.gif

176 ms

article-clipper-jp.png

article-clipper-jp.png

23 ms

logo_lineup_coressl.png

logo_lineup_coressl.png

1115 ms

hide_menu_01.gif

hide_menu_01.gif

353 ms

logo-tt.gif

logo-tt.gif

356 ms

hide_menu_02.gif

hide_menu_02.gif

359 ms

logo-wdl.gif

logo-wdl.gif

562 ms

hide_menu_03.gif

hide_menu_03.gif

396 ms

logo-fto.gif

logo-fto.gif

583 ms

hide_menu_04.gif

hide_menu_04.gif

686 ms

logo-photooo.gif

logo-photooo.gif

879 ms

logo.gif

logo.gif

913 ms

favorite.gif

favorite.gif

745 ms

sitemap_s.gif

sitemap_s.gif

932 ms

mail.gif

mail.gif

950 ms

btn_help.gif

btn_help.gif

1034 ms

btn_affiliate.gif

btn_affiliate.gif

1116 ms

navi_bg_fast.gif

navi_bg_fast.gif

1249 ms

navi_bg_shadow.gif

navi_bg_shadow.gif

1271 ms

navi_bg_off.gif

navi_bg_off.gif

1291 ms

navi_r.gif

navi_r.gif

1331 ms

pan.gif

pan.gif

1436 ms

button_off.gif

button_off.gif

1638 ms

rss_icon.gif

rss_icon.gif

1622 ms

58225-m.jpg

58225-m.jpg

1831 ms

spacer.gif

spacer.gif

1649 ms

57765-m.jpg

57765-m.jpg

1866 ms

58543-m.jpg

58543-m.jpg

2173 ms

58284-m.jpg

58284-m.jpg

2197 ms

58166-m.jpg

58166-m.jpg

2321 ms

57997-m.jpg

57997-m.jpg

2194 ms

58482-m.jpg

58482-m.jpg

2606 ms

58481-m.jpg

58481-m.jpg

2580 ms

58046-m.jpg

58046-m.jpg

2676 ms

top_search.gif

top_search.gif

2554 ms

top_support.jpg

top_support.jpg

3358 ms

color.gif

color.gif

2691 ms

search_button.gif

search_button.gif

2923 ms

side_t-tune.gif

side_t-tune.gif

3100 ms

share_4.png

share_4.png

26 ms

195 ms

like.php

like.php

85 ms

uh.js

uh.js

506 ms

analytics.js

analytics.js

31 ms

tag.js

tag.js

13 ms

40 ms

conversion.js

conversion.js

1164 ms

tag

tag

16 ms

linkid.js

linkid.js

14 ms

ec.js

ec.js

29 ms

48 ms

-1cfYrhulAt.js

-1cfYrhulAt.js

287 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

321 ms

collect

collect

16 ms

collect

collect

46 ms

ga-audiences

ga-audiences

18 ms

reset.css

reset.css

15 ms

entry-button.css

entry-button.css

15 ms

button-counter.gif

button-counter.gif

5 ms

1x1.gif

1x1.gif

383 ms

side_editpartner.gif

side_editpartner.gif

2780 ms

case.jpg

case.jpg

3359 ms

partner_bottom.gif

partner_bottom.gif

2697 ms

twitterlink.gif

twitterlink.gif

2897 ms

facebooklink.gif

facebooklink.gif

2831 ms

7th_back.jpg

7th_back.jpg

3401 ms

icon.gif

icon.gif

2783 ms

button_on.gif

button_on.gif

3086 ms

ribbon.png

ribbon.png

2833 ms

topblog_icon.gif

topblog_icon.gif

2856 ms

topblog_arrow.gif

topblog_arrow.gif

2902 ms

search_title.gif

search_title.gif

3103 ms

color_list.gif

color_list.gif

3040 ms

search_button_ov.gif

search_button_ov.gif

2989 ms

partner.gif

partner.gif

2938 ms

list_img_partner.gif

list_img_partner.gif

2919 ms

footer_pic.gif

footer_pic.gif

3044 ms

916 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

40 ms

ya.js

ya.js

367 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

19 ms

fastbutton

fastbutton

118 ms

bluearrow.gif

bluearrow.gif

3078 ms

postmessageRelay

postmessageRelay

48 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

17 ms

api.js

api.js

43 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

87 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

79 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

20 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

21 ms

grlryt2bdKIyfMSOhzd1eA.woff

grlryt2bdKIyfMSOhzd1eA.woff

101 ms

jot

jot

112 ms

pb.js

pb.js

560 ms

319 ms

396 ms

navi_f_01.gif

navi_f_01.gif

179 ms

navi_f_02.gif

navi_f_02.gif

196 ms

navi_f_03.gif

navi_f_03.gif

339 ms

navi_f_04.gif

navi_f_04.gif

366 ms

navi_f_05.gif

navi_f_05.gif

371 ms

navi_f_06.gif

navi_f_06.gif

389 ms

navi_f_07.gif

navi_f_07.gif

545 ms

navi_f_08.gif

navi_f_08.gif

568 ms

navi_f_09.gif

navi_f_09.gif

673 ms

navi_f_10.gif

navi_f_10.gif

709 ms

navi_f_11.gif

navi_f_11.gif

707 ms

navi_f_12.gif

navi_f_12.gif

745 ms

menu_f_01.gif

menu_f_01.gif

913 ms

menu_f_02.gif

menu_f_02.gif

914 ms

menu_f_03.gif

menu_f_03.gif

1045 ms

menu_f_04.gif

menu_f_04.gif

1043 ms

menu_f_05.gif

menu_f_05.gif

1075 ms

menu_f_06.gif

menu_f_06.gif

1104 ms

menu_f_07.gif

menu_f_07.gif

1281 ms

menu_f_08.gif

menu_f_08.gif

1289 ms

menu_f_09.gif

menu_f_09.gif

1387 ms

menu_f_10.gif

menu_f_10.gif

1398 ms

menu_f_11.gif

menu_f_11.gif

1456 ms

menu_f_12.gif

menu_f_12.gif

1450 ms

menu_f_13.gif

menu_f_13.gif

1638 ms

menu_f_14.gif

menu_f_14.gif

1657 ms

menu_f_15.gif

menu_f_15.gif

1733 ms

menu_f_16.gif

menu_f_16.gif

1764 ms

menu_f_18.gif

menu_f_18.gif

1816 ms

menu_f_19.gif

menu_f_19.gif

1826 ms

menu_f_20.gif

menu_f_20.gif

1985 ms

Accessibility Review

templatemonster.jp accessibility score

84

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

High

Links do not have a discernible name

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

templatemonster.jp SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Templatemonster.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 Templatemonster.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

templatemonster.jp

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