5.3 sec in total
325 ms
4.4 sec
523 ms
Welcome to matcher.jp homepage info - get ready to check Matcher best content for Japan right away, or after learning these important things about matcher.jp
Matcherは、国内最大級のOB訪問支援サービスです。大学の先輩以外でも、気になる企業の気になる人に気軽にOB訪問をすることができます!
Visit matcher.jpWe analyzed Matcher.jp page load time and found that the first response time was 325 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
matcher.jp performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value11.7 s
0/100
25%
Value7.7 s
24/100
10%
Value570 ms
52/100
30%
Value0
100/100
15%
Value10.1 s
26/100
10%
325 ms
2054 ms
1102 ms
506 ms
510 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 66% of them (43 requests) were addressed to the original Matcher.jp, 31% (20 requests) were made to S3-ap-northeast-1.amazonaws.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Matcher.jp.
Page size can be reduced by 487.0 kB (40%)
1.2 MB
742.2 kB
In fact, the total size of Matcher.jp main page is 1.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. 40% of websites need less resources to load. Images take 619.3 kB which makes up the majority of the site volume.
Potential reduce by 108.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 39.7 kB, which is 33% 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 108.4 kB or 89% of the original size.
Potential reduce by 20.3 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. Matcher images are well optimized though.
Potential reduce by 199.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 199.5 kB or 67% of the original size.
Potential reduce by 158.8 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. Matcher.jp needs all CSS files to be minified and compressed as it can save up to 158.8 kB or 83% of the original size.
Number of requests can be reduced by 21 (34%)
62
41
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Matcher. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
matcher.jp
325 ms
matcher.jp
2054 ms
bootstrap.min.css
1102 ms
jasny-bootstrap.min.css
506 ms
common.css
510 ms
style.css
661 ms
sp.css
519 ms
darktooltip.css
622 ms
pnotify.custom.min.css
662 ms
bootstrap-same-row-height.css
669 ms
jquery.min.js
1190 ms
clean_query.js
326 ms
jquery.pjax.js
566 ms
jasny-bootstrap.min.js
564 ms
bootstrap.min.js
577 ms
util.js
521 ms
trunk8.js
716 ms
jquery.darktooltip.js
775 ms
jquery.cookie.js
775 ms
pnotify.custom.min.js
775 ms
jquery.matchHeight-min.js
858 ms
jquery.wookmark.js
898 ms
masonry.pkgd.min.js
945 ms
jquery.raty.js
954 ms
analytics.js
59 ms
941.jpg
673 ms
matcher_logo_w.png
203 ms
scroll_top.png
320 ms
icon-white-facebook.png
320 ms
631.jpg
691 ms
715.jpg
699 ms
432.jpg
709 ms
1417.jpg
697 ms
581.jpg
716 ms
1776.jpg
857 ms
1595.jpg
867 ms
2045.jpg
880 ms
2044.jpg
889 ms
1703.jpg
874 ms
396.jpg
893 ms
424.jpg
1036 ms
2042.jpg
1052 ms
1709.jpg
1054 ms
1317.jpg
1057 ms
2035.jpg
1067 ms
1108.jpg
1092 ms
870.jpg
1210 ms
1669.jpg
1244 ms
eyecatch.jpg
609 ms
line.png
343 ms
glyphicons-halflings-regular.woff
338 ms
2.jpg
477 ms
13.jpg
346 ms
6.jpg
346 ms
12.jpg
478 ms
1.jpg
686 ms
8.jpg
667 ms
3.jpg
680 ms
11.jpg
808 ms
10.jpg
816 ms
9.jpg
733 ms
18.jpg
832 ms
collect
22 ms
star-on.png
587 ms
star-off.png
592 ms
matcher.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
matcher.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
matcher.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Matcher.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 Matcher.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.
matcher.jp
Open Graph data is detected on the main page of Matcher. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: