Report Summary

  • 64

    Performance

    Renders faster than
    78% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

e-kensin.net

北海道建設新聞社 - e-kensin

Page Load Speed

8 sec in total

First Response

1.1 sec

Resources Loaded

6.7 sec

Page Rendered

185 ms

e-kensin.net screenshot

About Website

Visit e-kensin.net now to see the best up-to-date E Kensin content for Japan and also check out these interesting facts you probably never knew about e-kensin.net

帯広建管、九号川通常砂防で24年度以降に10.9億円見込む - 北海道建設新聞社 - e-kensin

Visit e-kensin.net

Key Findings

We analyzed E-kensin.net page load time and found that the first response time was 1.1 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

e-kensin.net performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value5.2 s

73/100

10%

Network Requests Diagram

e-kensin.net

1069 ms

import.css

335 ms

jquery.js

696 ms

rollover.js

369 ms

dropdown.js

365 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 80% of them (80 requests) were addressed to the original E-kensin.net, 3% (3 requests) were made to Ad.linksynergy.com and 2% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain E-kensin.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 473.9 kB (58%)

Content Size

817.5 kB

After Optimization

343.6 kB

In fact, the total size of E-kensin.net main page is 817.5 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. 40% of websites need less resources to load. Javascripts take 317.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 46.9 kB

  • Original 58.7 kB
  • After minification 44.5 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 14.3 kB, which is 24% 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 46.9 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 11.7 kB

  • Original 175.5 kB
  • After minification 163.8 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. E Kensin images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 194.4 kB

  • Original 317.0 kB
  • After minification 316.4 kB
  • After compression 122.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 194.4 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 220.8 kB

  • Original 266.2 kB
  • After minification 262.1 kB
  • After compression 45.4 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. E-kensin.net needs all CSS files to be minified and compressed as it can save up to 220.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (44%)

Requests Now

95

After Optimization

53

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

Accessibility Review

e-kensin.net accessibility score

71

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

e-kensin.net best practices score

75

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

SEO Factors

e-kensin.net SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 E-kensin.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 E-kensin.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

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