Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

jmatch.jp

Jエンジン|Jエンジンは、中小企業に特化した経営支援サービスです。全国、全ての中小企業を黒字にすることを真剣に考えています。

Page Load Speed

14.7 sec in total

First Response

566 ms

Resources Loaded

12.9 sec

Page Rendered

1.2 sec

jmatch.jp screenshot

About Website

Click here to check amazing Jmatch content for Japan. Otherwise, check out these important facts you probably never knew about jmatch.jp

Jエンジンは、公的支援制度(補助金・助成金・融資)活用支援サービスです。中小企業の経営者を徹底的に応援します。

Visit jmatch.jp

Key Findings

We analyzed Jmatch.jp page load time and found that the first response time was 566 ms and then it took 14.1 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

jmatch.jp performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value18.6 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

jmatch.jp

566 ms

www.jmatch.jp

1572 ms

normalize.min.css

523 ms

flexslider.css

532 ms

base.css

897 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 66% of them (61 requests) were addressed to the original Jmatch.jp, 9% (8 requests) were made to Apis.google.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (7.7 sec) belongs to the original domain Jmatch.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 257.4 kB (4%)

Content Size

6.8 MB

After Optimization

6.5 MB

In fact, the total size of Jmatch.jp main page is 6.8 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 6.5 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 38.7 kB

  • Original 52.1 kB
  • After minification 50.6 kB
  • After compression 13.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. 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 38.7 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 39.2 kB

  • Original 6.5 MB
  • After minification 6.4 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. Jmatch images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 125.0 kB

  • Original 201.7 kB
  • After minification 183.7 kB
  • After compression 76.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 125.0 kB or 62% of the original size.

CSS Optimization

-80%

Potential reduce by 54.4 kB

  • Original 67.6 kB
  • After minification 55.3 kB
  • After compression 13.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. Jmatch.jp needs all CSS files to be minified and compressed as it can save up to 54.4 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (32%)

Requests Now

90

After Optimization

61

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

Accessibility Review

jmatch.jp accessibility score

75

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

jmatch.jp best practices score

58

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

jmatch.jp SEO score

90

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jmatch.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 Jmatch.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 data is detected on the main page of Jmatch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: