Tools & Wizards About Us
webtan.net screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

webtan.net

エックスサーバー サーバー初期ページ

Page Load Speed

7 sec in total

First Response

1.5 sec

Resources Loaded

5.2 sec

Page Rendered

259 ms

webtan.net screenshot

About Website

Welcome to webtan.net homepage info - get ready to check Webtan best content right away, or after learning these important things about webtan.net

ホームページ作成、サイト運営のノウハウ。Web担当者目線の入門サイト。

Visit webtan.net

Key Findings

We analyzed Webtan.net page load time and found that the first response time was 1.5 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

webtan.net performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value1.1 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

webtan.net

1478 ms

811f64f28710562e6aac9b2ac137f960.b64.css

556 ms

styles.css

387 ms

screen.css

389 ms

css3_red.css

418 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 48% of them (38 requests) were addressed to the original Webtan.net, 11% (9 requests) were made to Google.com and 9% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Webtan.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 207.9 kB (18%)

Content Size

1.1 MB

After Optimization

932.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Webtan.net 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. 55% of websites need less resources to load. Images take 697.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 40.2 kB

  • Original 51.1 kB
  • After minification 48.9 kB
  • After compression 10.9 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 40.2 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 7.8 kB

  • Original 697.9 kB
  • After minification 690.1 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. Webtan images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 136.1 kB

  • Original 358.3 kB
  • After minification 356.3 kB
  • After compression 222.1 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 136.1 kB or 38% of the original size.

CSS Optimization

-72%

Potential reduce by 23.8 kB

  • Original 33.1 kB
  • After minification 30.1 kB
  • After compression 9.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. Webtan.net needs all CSS files to be minified and compressed as it can save up to 23.8 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (41%)

Requests Now

76

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webtan.net

webtan.net

1478 ms

811f64f28710562e6aac9b2ac137f960.b64.css

811f64f28710562e6aac9b2ac137f960.b64.css

556 ms

styles.css

styles.css

387 ms

screen.css

screen.css

389 ms

css3_red.css

css3_red.css

418 ms

adsbygoogle.js

adsbygoogle.js

8 ms

top_img.png

top_img.png

1004 ms

top_h2_catch.png

top_h2_catch.png

665 ms

75e74f6baba1d9692175c0bfd887cf41.jpg

75e74f6baba1d9692175c0bfd887cf41.jpg

1126 ms

webtan-blog.png

webtan-blog.png

1062 ms

98edb1a6ed4360b66d24afb4a1ed7bb1.jpg

98edb1a6ed4360b66d24afb4a1ed7bb1.jpg

1208 ms

beginner-class.png

beginner-class.png

1061 ms

a5c4bb53a2a5a2b18e223fc9da8b09bb.jpg

a5c4bb53a2a5a2b18e223fc9da8b09bb.jpg

1242 ms

intermediate-class.png

intermediate-class.png

1225 ms

c4020b1f68df75d112cc456736290510.jpg

c4020b1f68df75d112cc456736290510.jpg

1901 ms

fcedeb3e47d759777985cdd471841cd1.jpg

fcedeb3e47d759777985cdd471841cd1.jpg

1763 ms

advanced-class.png

advanced-class.png

2210 ms

99ca0d3bd4e44316dcf8ee525cd6f876.jpg

99ca0d3bd4e44316dcf8ee525cd6f876.jpg

1977 ms

4e31cb84d3f140430ce5d7b92b425bd1.png

4e31cb84d3f140430ce5d7b92b425bd1.png

2167 ms

76c040cb79a8466eb724ddddbd2396ae.png

76c040cb79a8466eb724ddddbd2396ae.png

2189 ms

analyze.js

analyze.js

768 ms

script.php

script.php

1105 ms

jquery.min.js

jquery.min.js

15 ms

plusone.js

plusone.js

57 ms

js_css.php

js_css.php

2753 ms

ca-pub-6876288970765607.js

ca-pub-6876288970765607.js

108 ms

zrt_lookup.html

zrt_lookup.html

104 ms

show_ads_impl.js

show_ads_impl.js

63 ms

gplus-32.png

gplus-32.png

61 ms

side_new_release.png

side_new_release.png

1686 ms

side_popular_articles.png

side_popular_articles.png

1880 ms

1321edd9d222b1a626e3dd31ceeb7feb.jpg

1321edd9d222b1a626e3dd31ceeb7feb.jpg

1840 ms

e94804129a22cb41ea32d223d6c9e5ae1.jpg

e94804129a22cb41ea32d223d6c9e5ae1.jpg

2461 ms

fdaf8633e72b74733f4b191aa15a0792.png

fdaf8633e72b74733f4b191aa15a0792.png

2439 ms

8ae4f89d0138457f4093c1b13e63012d.jpg

8ae4f89d0138457f4093c1b13e63012d.jpg

2234 ms

side_cate_01.png

side_cate_01.png

2243 ms

side_cate_02.png

side_cate_02.png

2281 ms

side_cate_03.png

side_cate_03.png

2440 ms

side_cate_04.png

side_cate_04.png

2644 ms

side_cate_05.png

side_cate_05.png

2681 ms

rss_img.png

rss_img.png

2563 ms

top_link.png

top_link.png

2624 ms

b7246a5ea2190283ce85f2c516ed6456.png

b7246a5ea2190283ce85f2c516ed6456.png

3315 ms

2aa49c24560478bbba3b6202ad6f6356.jpg

2aa49c24560478bbba3b6202ad6f6356.jpg

2666 ms

58f46e70c3aa1777bd4b0511eeccaad5.png

58f46e70c3aa1777bd4b0511eeccaad5.png

3341 ms

banner_13.gif

banner_13.gif

2846 ms

counter.png

counter.png

494 ms

cse.js

cse.js

71 ms

ads

ads

275 ms

osd.js

osd.js

11 ms

cse.js

cse.js

56 ms

ads

ads

236 ms

ads

ads

207 ms

jsapi

jsapi

32 ms

default+ja.css

default+ja.css

4 ms

minimalist.css

minimalist.css

30 ms

default+ja.I.js

default+ja.I.js

14 ms

minimalist.css

minimalist.css

9 ms

3282744251703269152

3282744251703269152

99 ms

abg.js

abg.js

48 ms

m_js_controller.js

m_js_controller.js

57 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

94 ms

13337325976321899390

13337325976321899390

91 ms

analyze.png

analyze.png

597 ms

s

s

45 ms

x_button_blue2.png

x_button_blue2.png

41 ms

favicon

favicon

84 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

12 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

2 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

activeview

activeview

14 ms

activeview

activeview

15 ms

analytics.js

analytics.js

63 ms

async-ads.js

async-ads.js

39 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

34 ms

small-logo.png

small-logo.png

29 ms

clear.gif

clear.gif

29 ms

nav_logo114.png

nav_logo114.png

8 ms

ajax-loader.gif

ajax-loader.gif

482 ms

collect

collect

13 ms

Accessibility Review

webtan.net accessibility score

100

Accessibility Issues

Best Practices

webtan.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

webtan.net SEO score

64

Search Engine Optimization Advices

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 Webtan.net 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 Webtan.net 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

webtan.net

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