Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

tech-tokachi.jp

公益財団法人とかち財団/十勝のビジネスをサポート

Page Load Speed

11.5 sec in total

First Response

2.2 sec

Resources Loaded

8.8 sec

Page Rendered

511 ms

About Website

Click here to check amazing Tech Tokachi content. Otherwise, check out these important facts you probably never knew about tech-tokachi.jp

技術開発から販路拡大まで、十勝の事業者様の「ものづくり」をトータルでサポートする「公益財団法人とかち財団」のホームページです。機械/電子・食品・企業支援/助成金・地域連携などを情報を更新中!

Visit tech-tokachi.jp

Key Findings

We analyzed Tech-tokachi.jp page load time and found that the first response time was 2.2 sec and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

tech-tokachi.jp performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

www.tokachi-zaidan.jp

2162 ms

css_control_page.js

487 ms

jquery-1.11.2.min.js

1151 ms

jquery.easing-1.3.js

494 ms

module_page.js

557 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Tech-tokachi.jp, 4% (4 requests) were made to Maps.googleapis.com and 2% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Tokachi-zaidan.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (24%)

Content Size

5.2 MB

After Optimization

4.0 MB

In fact, the total size of Tech-tokachi.jp main page is 5.2 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. 65% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 86.6 kB

  • Original 100.6 kB
  • After minification 92.1 kB
  • After compression 14.0 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 86.6 kB or 86% of the original size.

Image Optimization

-15%

Potential reduce by 687.1 kB

  • Original 4.5 MB
  • After minification 3.8 MB

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. Obviously, Tech Tokachi needs image optimization as it can save up to 687.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 262.0 kB

  • Original 393.1 kB
  • After minification 385.5 kB
  • After compression 131.0 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 262.0 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 213.9 kB

  • Original 248.9 kB
  • After minification 180.3 kB
  • After compression 35.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. Tech-tokachi.jp needs all CSS files to be minified and compressed as it can save up to 213.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (33%)

Requests Now

105

After Optimization

70

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

Accessibility Review

tech-tokachi.jp accessibility score

74

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

High

Links do not have a discernible name

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

tech-tokachi.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

tech-tokachi.jp SEO score

90

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

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