Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

mathtext.info

数学問題提供サイト(数樂)数学の問題集(受験数学)|受験算数|中学数学|高校数学|

Page Load Speed

6.1 sec in total

First Response

871 ms

Resources Loaded

5 sec

Page Rendered

198 ms

mathtext.info screenshot

About Website

Visit mathtext.info now to see the best up-to-date Mathtext content for Japan and also check out these interesting facts you probably never knew about mathtext.info

中学受験の算数、高校受験(中学数学)、大学受験(高校数学)など。メインは中学受験(算数),高校受験(中学数学),大学受験(高校数学)の問題を提供するサイト。問題の攻略方法や裏技、 生徒の疑問(なんで?なぜ?)、などを紹介しています。問題はオリジナル問題から入試問題まであります。数学を楽しみたい人、数学が面白いと思う人は是非遊んでいってください。

Visit mathtext.info

Key Findings

We analyzed Mathtext.info page load time and found that the first response time was 871 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

mathtext.info performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value410 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.187

65/100

15%

TTI (Time to Interactive)

Value13.7 s

11/100

10%

Network Requests Diagram

mathtext.info

871 ms

arthref.css

492 ms

stylesheet1.css

512 ms

stylesheet2.css

513 ms

amazonmenu.css

348 ms

Our browser made a total of 150 requests to load all elements on the main page. We found that 26% of them (39 requests) were addressed to the original Mathtext.info, 15% (23 requests) were made to Static.xx.fbcdn.net and 6% (9 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Mathtext.info.

Page Optimization Overview & Recommendations

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

Content Size

1.4 MB

After Optimization

903.7 kB

In fact, the total size of Mathtext.info main page is 1.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 782.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 26.0 kB

  • Original 34.2 kB
  • After minification 27.4 kB
  • After compression 8.1 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 6.8 kB, which is 20% 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 26.0 kB or 76% of the original size.

Image Optimization

-13%

Potential reduce by 102.5 kB

  • Original 782.6 kB
  • After minification 680.1 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, Mathtext needs image optimization as it can save up to 102.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-61%

Potential reduce by 310.2 kB

  • Original 509.4 kB
  • After minification 497.6 kB
  • After compression 199.2 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 310.2 kB or 61% of the original size.

CSS Optimization

-82%

Potential reduce by 76.3 kB

  • Original 92.6 kB
  • After minification 85.3 kB
  • After compression 16.2 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. Mathtext.info needs all CSS files to be minified and compressed as it can save up to 76.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 75 (52%)

Requests Now

143

After Optimization

68

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

Accessibility Review

mathtext.info accessibility score

59

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

mathtext.info 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

mathtext.info SEO score

86

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 Mathtext.info 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 Mathtext.info 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 Mathtext. 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: