Tools & Wizards About Us
town-guide.jp screenshot

Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

town-guide.jp

タウンガイド | 全国の地域情報コミュニティ

Page Load Speed

2.3 sec in total

First Response

270 ms

Resources Loaded

1.8 sec

Page Rendered

228 ms

town-guide.jp screenshot

About Website

Click here to check amazing Town Guide content for Japan. Otherwise, check out these important facts you probably never knew about town-guide.jp

タウンガイド情報満載、地元密着情報コミュニティポータルサイト「タウンガイド」

Visit town-guide.jp

Key Findings

We analyzed Town-guide.jp page load time and found that the first response time was 270 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

town-guide.jp performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.3 s

100/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.183

66/100

15%

TTI (Time to Interactive)

Value1.3 s

100/100

10%

Network Requests Diagram

270 ms

style.css

184 ms

show_ads.js

10 ms

image_top.gif

527 ms

top_image.gif

409 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 39% of them (13 requests) were addressed to the original Town-guide.jp, 21% (7 requests) were made to Tpc.googlesyndication.com and 18% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (671 ms) relates to the external source Town-guide.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.9 kB (12%)

Content Size

251.8 kB

After Optimization

220.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Town-guide.jp main page is 251.8 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 200.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 12.5 kB

  • Original 16.6 kB
  • After minification 15.5 kB
  • After compression 4.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 12.5 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 4.8 kB

  • Original 200.4 kB
  • After minification 195.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. Town Guide images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 9.8 kB

  • Original 30.4 kB
  • After minification 30.3 kB
  • After compression 20.7 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 9.8 kB or 32% of the original size.

CSS Optimization

-90%

Potential reduce by 3.8 kB

  • Original 4.3 kB
  • After minification 2.6 kB
  • After compression 438 B

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. Town-guide.jp needs all CSS files to be minified and compressed as it can save up to 3.8 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (16%)

Requests Now

31

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

270 ms

style.css

style.css

184 ms

show_ads.js

show_ads.js

10 ms

image_top.gif

image_top.gif

527 ms

top_image.gif

top_image.gif

409 ms

zrt_lookup.html

zrt_lookup.html

43 ms

show_ads_impl.js

show_ads_impl.js

50 ms

sumaho.png

sumaho.png

671 ms

back_top.gif

back_top.gif

375 ms

t2.gif

t2.gif

504 ms

t3.gif

t3.gif

505 ms

t4.gif

t4.gif

583 ms

t5.gif

t5.gif

582 ms

t8.gif

t8.gif

573 ms

QR_Code.jpg

QR_Code.jpg

583 ms

s1.gif

s1.gif

670 ms

image_foot1.gif

image_foot1.gif

666 ms

ads

ads

222 ms

osd.js

osd.js

41 ms

ads

ads

266 ms

ads

ads

298 ms

ads

ads

308 ms

15122106571364463425

15122106571364463425

32 ms

abg.js

abg.js

32 ms

m_js_controller.js

m_js_controller.js

41 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

98 ms

s

s

51 ms

x_button_blue2.png

x_button_blue2.png

49 ms

favicon

favicon

169 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

5 ms

104567748280258855

104567748280258855

25 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

39 ms

4616892906042616458

4616892906042616458

99 ms

Accessibility Review

town-guide.jp accessibility score

74

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

town-guide.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

town-guide.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

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Town-guide.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Town-guide.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

town-guide.jp

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