Tools & Wizards About Us
ma-times.jp screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ma-times.jp

M＆Aニュース配信量NO.1サイト｜Ｍ＆Ａ ニュース速報 | Ｍ＆Ａ タイムス

Page Load Speed

5.6 sec in total

First Response

557 ms

Resources Loaded

4.8 sec

Page Rendered

284 ms

ma-times.jp screenshot

About Website

Welcome to ma-times.jp homepage info - get ready to check Ma Times best content for Japan right away, or after learning these important things about ma-times.jp

Ｍ＆Ａ ニュース配信量No.1 サイト、Ｍ＆Ａ タイムスは企業買収・合併・資本提携を始めとした最新のM&Aに関する情報はもちろん、倒産・民事再生・新規IPO情報など企業の動向がわかるビジネスエグゼクティブに向けたM&Aのニュースサイトです。

Visit ma-times.jp

Key Findings

We analyzed Ma-times.jp page load time and found that the first response time was 557 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ma-times.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value3,030 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value1.212

1/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

ma-times.jp

557 ms

ma-times.jp

1509 ms

reset.css

185 ms

style.css

369 ms

slick.css

536 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 68% of them (54 requests) were addressed to the original Ma-times.jp, 8% (6 requests) were made to Tpc.googlesyndication.com and 4% (3 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Ma-times.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 327.4 kB (36%)

Content Size

898.3 kB

After Optimization

571.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ma-times.jp main page is 898.3 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. 60% of websites need less resources to load. Javascripts take 458.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 63.9 kB

  • Original 80.1 kB
  • After minification 80.1 kB
  • After compression 16.2 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 63.9 kB or 80% of the original size.

Image Optimization

-14%

Potential reduce by 44.8 kB

  • Original 321.7 kB
  • After minification 276.9 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. Obviously, Ma Times needs image optimization as it can save up to 44.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-46%

Potential reduce by 210.3 kB

  • Original 458.1 kB
  • After minification 458.1 kB
  • After compression 247.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 210.3 kB or 46% of the original size.

CSS Optimization

-22%

Potential reduce by 8.4 kB

  • Original 38.5 kB
  • After minification 38.0 kB
  • After compression 30.1 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. Ma-times.jp needs all CSS files to be minified and compressed as it can save up to 8.4 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (49%)

Requests Now

74

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ma-times.jp

ma-times.jp

557 ms

ma-times.jp

ma-times.jp

1509 ms

reset.css

reset.css

185 ms

style.css

style.css

369 ms

slick.css

slick.css

536 ms

slick-theme.css

slick-theme.css

551 ms

swiper.min.css

swiper.min.css

550 ms

header-2017.css

header-2017.css

552 ms

footer-2017.css

footer-2017.css

558 ms

parts-2017.css

parts-2017.css

557 ms

common-2017.css

common-2017.css

714 ms

2019-common.css

2019-common.css

732 ms

2019-contents.css

2019-contents.css

734 ms

2019-parts.css

2019-parts.css

734 ms

2019-contents.css

2019-contents.css

740 ms

jquery.min.1.11.3.js

jquery.min.1.11.3.js

932 ms

jquery.jscroll.min.js

jquery.jscroll.min.js

895 ms

jquery.inview.min.js

jquery.inview.min.js

919 ms

test-jscroll.js

test-jscroll.js

918 ms

adsbygoogle.js

adsbygoogle.js

160 ms

validationEngine.jquery.css

validationEngine.jquery.css

917 ms

style.min.css

style.min.css

1111 ms

wpp.css

wpp.css

1087 ms

wpp.min.js

wpp.min.js

1106 ms

slick.min.js

slick.min.js

1106 ms

analytics.js

analytics.js

45 ms

gpt.js

gpt.js

114 ms

collect

collect

14 ms

js

js

72 ms

pubads_impl.js

pubads_impl.js

47 ms

whitelogo.png

whitelogo.png

244 ms

icon-facebook.png

icon-facebook.png

244 ms

icon-twitter.png

icon-twitter.png

244 ms

icon-feedly.png

icon-feedly.png

243 ms

icon-search.png

icon-search.png

244 ms

0-VT.jpg

0-VT.jpg

243 ms

meiko.jpg

meiko.jpg

372 ms

Usen-Next_Holding.jpg

Usen-Next_Holding.jpg

372 ms

0-VT-11.jpg

0-VT-11.jpg

373 ms

0-VT-10.jpg

0-VT-10.jpg

365 ms

0-VT-9.jpg

0-VT-9.jpg

375 ms

0-VT-8.jpg

0-VT-8.jpg

375 ms

0-VT-7.jpg

0-VT-7.jpg

543 ms

0-VT-6.jpg

0-VT-6.jpg

552 ms

0-VT-5.jpg

0-VT-5.jpg

553 ms

0-VT-9.jpg

0-VT-9.jpg

554 ms

0-VT-4.jpg

0-VT-4.jpg

558 ms

0-VT-4-240x180.jpg

0-VT-4-240x180.jpg

558 ms

%E3%82%AD%E3%83%A3%E3%83%97%E3%83%81%E3%83%A355.jpg

%E3%82%AD%E3%83%A3%E3%83%97%E3%83%81%E3%83%A355.jpg

903 ms

6866.1-240x180.jpg

6866.1-240x180.jpg

741 ms

6753.1-240x180.jpg

6753.1-240x180.jpg

741 ms

tekuno-240x180.png

tekuno-240x180.png

922 ms

pbanner.png

pbanner.png

927 ms

icon-total-like.png

icon-total-like.png

743 ms

vt-banner.jpg

vt-banner.jpg

923 ms

lf-banner.jpg

lf-banner.jpg

1104 ms

sdk.js

sdk.js

107 ms

bg.png

bg.png

915 ms

1895902133.js

1895902133.js

125 ms

ads

ads

431 ms

container.html

container.html

35 ms

sdk.js

sdk.js

10 ms

ajax-loader.gif

ajax-loader.gif

1000 ms

slick.woff

slick.woff

1015 ms

49 ms

load_preloaded_resource.js

load_preloaded_resource.js

21 ms

icon.png

icon.png

15 ms

abg_lite.js

abg_lite.js

24 ms

s

s

22 ms

window_focus.js

window_focus.js

29 ms

qs_click_protection.js

qs_click_protection.js

32 ms

5f7468413707c3abfd197d65a482477f.js

5f7468413707c3abfd197d65a482477f.js

22 ms

css

css

32 ms

1FsAZVbOrk0KoHU6IIV-PEky-2wi5E8kHH2hPfG7_LM.js

1FsAZVbOrk0KoHU6IIV-PEky-2wi5E8kHH2hPfG7_LM.js

7 ms

font

font

16 ms

sodar

sodar

74 ms

slick.ttf

slick.ttf

295 ms

sodar2.js

sodar2.js

5 ms

runner.html

runner.html

5 ms

aframe

aframe

23 ms

Accessibility Review

ma-times.jp accessibility score

61

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.

High

ARIA toggle fields do not have accessible names

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

Buttons do not have an accessible name

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

[id] attributes on active, focusable elements are not unique

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

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

ma-times.jp best practices score

67

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ma-times.jp SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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

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 Ma-times.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 Ma-times.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

ma-times.jp

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