Tools & Wizards About Us
sekigin.jp screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

sekigin.jp

技術情報館「SEKIGIN」(セキジン)｜鉄道や道路を中心にインフラの歴史と現状，鋼橋の維持管理，鋼を中心とする金属腐食，防食・防せいに用いる材料として塗料・塗装，めっき，溶射などの技術，生活の中の科学に関連する基礎化学・物理など，技術者に役立つ情報提供を目的とするサイトである。

Page Load Speed

4.4 sec in total

First Response

712 ms

Resources Loaded

2.7 sec

Page Rendered

1 sec

sekigin.jp screenshot

About Website

Visit sekigin.jp now to see the best up-to-date SEKIGIN content for Japan and also check out these interesting facts you probably never knew about sekigin.jp

技術情報館 SIKIGIN（セキジン）では，道路，鉄道を初めとする社会資本の維持管理に資することを目的に，鉄道，道路，港湾，電力などのインフラの歴史と現状の紹介，鋼橋など鋼構造物の設計・製造・維持・管理・腐食・防食について，総合的な技術情報提供を目的に活動します。特に，維持管理技術者が不得意とする腐食，防食技術の理解を助けるため，金属材料，腐食現象，防食対策を紹介します。さらには，インフラに関連す...

Visit sekigin.jp

Key Findings

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

Performance Metrics

sekigin.jp performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value9.9 s

9/100

10%

TBT (Total Blocking Time)

Value31,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value40.1 s

0/100

10%

Network Requests Diagram

sekigin.jp

712 ms

style1.css

342 ms

adsbygoogle.js

52 ms

show_ads_impl.js

92 ms

zrt_lookup.html

86 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Sekigin.jp, 23% (9 requests) were made to Googleads.g.doubleclick.net and 20% (8 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (757 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 66.5 kB (27%)

Content Size

246.2 kB

After Optimization

179.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 50.0 kB

  • Original 62.4 kB
  • After minification 51.1 kB
  • After compression 12.4 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 11.3 kB, which is 18% 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 50.0 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 11.3 kB

  • Original 159.3 kB
  • After minification 148.0 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. SEKIGIN images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 338 B

  • Original 18.8 kB
  • After minification 18.8 kB
  • After compression 18.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-86%

Potential reduce by 4.9 kB

  • Original 5.7 kB
  • After minification 2.5 kB
  • After compression 813 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. Sekigin.jp needs all CSS files to be minified and compressed as it can save up to 4.9 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

37

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sekigin.jp

sekigin.jp

712 ms

style1.css

style1.css

342 ms

adsbygoogle.js

adsbygoogle.js

52 ms

show_ads_impl.js

show_ads_impl.js

92 ms

zrt_lookup.html

zrt_lookup.html

86 ms

cookie.js

cookie.js

57 ms

integrator.js

integrator.js

57 ms

ads

ads

556 ms

gradation1.png

gradation1.png

173 ms

integrator.js

integrator.js

22 ms

ads

ads

692 ms

ads

ads

757 ms

reactive_library.js

reactive_library.js

179 ms

ca-pub-2941308770496877

ca-pub-2941308770496877

213 ms

integrator.js

integrator.js

74 ms

ads

ads

752 ms

ads

ads

153 ms

zrt_lookup.html

zrt_lookup.html

68 ms

css2

css2

68 ms

991399821989149669

991399821989149669

294 ms

load_preloaded_resource.js

load_preloaded_resource.js

296 ms

abg_lite.js

abg_lite.js

299 ms

window_focus.js

window_focus.js

312 ms

qs_click_protection.js

qs_click_protection.js

319 ms

rx_lidar.js

rx_lidar.js

81 ms

042791247ab671b2831aa311d6583330.js

042791247ab671b2831aa311d6583330.js

73 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

306 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

538 ms

icon.png

icon.png

19 ms

15832494417852454100

15832494417852454100

537 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

63 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

73 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

32 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

40 ms

s

s

248 ms

redir.html

redir.html

385 ms

redir.html

redir.html

391 ms

activeview

activeview

128 ms

iframe.html

iframe.html

239 ms

-Y38d37a1DmvdXzRnIUkD6jTpQ2urOaWudC6FG_jR1g.js

-Y38d37a1DmvdXzRnIUkD6jTpQ2urOaWudC6FG_jR1g.js

4 ms

Accessibility Review

sekigin.jp accessibility score

72

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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.

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

sekigin.jp best practices score

92

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

Page has valid source maps

SEO Factors

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sekigin.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 Sekigin.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.

Social Sharing Optimization

sekigin.jp

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