6.1 sec in total
871 ms
5 sec
198 ms
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.infoWe 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.
mathtext.info performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value10.8 s
0/100
25%
Value9.5 s
12/100
10%
Value410 ms
66/100
30%
Value0.187
65/100
15%
Value13.7 s
11/100
10%
871 ms
492 ms
512 ms
513 ms
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 size can be reduced by 515.0 kB (36%)
1.4 MB
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.
Potential reduce by 26.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. 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.
Potential reduce by 102.5 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.
Potential reduce by 310.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.
Potential reduce by 76.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. 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.
Number of requests can be reduced by 75 (52%)
143
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.
mathtext.info
871 ms
arthref.css
492 ms
stylesheet1.css
512 ms
stylesheet2.css
513 ms
amazonmenu.css
348 ms
jquery-2.1.1.min.js
120 ms
jquery.easing.1.3.js
529 ms
jquery-ui-1.8.16.custom.min.js
1360 ms
jquery.animate-colors-min.js
528 ms
jquery.skitter.min.js
1032 ms
amazonmenu.js
726 ms
acodion.js
734 ms
platform.js
87 ms
widgets.js
151 ms
show_ads.js
19 ms
adsbygoogle.js
26 ms
topbar.png
637 ms
youtube1.png
1116 ms
icon1.png
439 ms
icon2.png
436 ms
icon3.png
426 ms
icon4.png
426 ms
icon5.png
573 ms
icon6.png
615 ms
icon7.png
614 ms
icon8.png
1093 ms
icon9.png
1082 ms
icon10.png
1091 ms
icon11.png
1090 ms
icon12.png
1125 ms
icon13.png
1299 ms
icon14.png
1300 ms
situmon.png
1460 ms
now_on.png
1796 ms
daycount.cgi
1343 ms
main.cgi
1305 ms
daycount.cgi
3030 ms
daycount.cgi
2099 ms
analytics.js
20 ms
sdk.js
113 ms
facebook.jpg
1601 ms
collect
27 ms
twitter.jpg
1641 ms
youtube.jpg
1611 ms
1918 ms
insta.jpg
1664 ms
backg.png
1544 ms
ca-pub-9726696955510277.js
173 ms
zrt_lookup.html
167 ms
show_ads_impl.js
96 ms
251 ms
timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js
326 ms
button.71000885400e222c3c0eec823f8f93f0.js
351 ms
cb=gapi.loaded_0
165 ms
cb=gapi.loaded_1
150 ms
sharebutton
215 ms
ads
296 ms
select.png
1346 ms
xd_arbiter.php
187 ms
xd_arbiter.php
266 ms
osd.js
65 ms
ads
297 ms
ads
343 ms
postmessageRelay
149 ms
rs=AGLTcCP9IczaT7Rf-UGgqDPBu0TrwouL5A
45 ms
rs=AGLTcCOmzMBdWlmm4GEO1m0aDMzKi6APzA
32 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
115 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
126 ms
like_box.php
860 ms
like.php
157 ms
1077434459-postmessagerelay.js
22 ms
rpc:shindig_random.js
38 ms
syndication
204 ms
330691485458644993
429 ms
m_js_controller.js
116 ms
abg.js
129 ms
cb=gapi.loaded_0
29 ms
tweet_button.fd774b599f565016d763dd860cb31c79.ja.html
66 ms
googlelogo_color_112x36dp.png
150 ms
16638132425042660108
82 ms
3082755850231251721
29 ms
3XaI8mzWBSs.js
276 ms
LVx-xkvaJ0b.png
307 ms
favicon
156 ms
nessie_icon_tiamat_white.png
70 ms
s
63 ms
x_button_blue2.png
16 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
9 ms
proxy.jpg
57 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
77 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
107 ms
9J9P0jqM_normal.jpg
238 ms
AdH_pg9w_normal.png
543 ms
CXselGbU0AA9d32.jpg:small
548 ms
syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css
235 ms
syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css
264 ms
cvGwopP4Ypw.css
33 ms
NZrHbW9qaLZ.css
59 ms
9FJPnd6A9bg.css
77 ms
jLkXrGcBOhb.css
109 ms
REjEQ583IyS.css
99 ms
SRSW8M763HA.js
121 ms
ldIMPsSoKmy.js
121 ms
y97Ig99UVTs.js
78 ms
KHAtULXOQuz.js
97 ms
W4NL_XloU4d.js
96 ms
eACiSk3I2K6.js
154 ms
FOagnU9QnXq.js
161 ms
rR4Qw0p7TFQ.js
180 ms
ULtnh-HfQSw.js
160 ms
6IFzBT9uHU-.js
160 ms
426949_202866063152603_689366102_n.jpg
387 ms
safe_image.php
335 ms
ye4Amg-qrtc.js
24 ms
safe_image.php
335 ms
402718_190608607711682_488049692_n.jpg
320 ms
12919832_1064956446881235_670581451447121305_n.png
496 ms
1623777_1426131154293935_1265355892_n.png
321 ms
12920503_1031556476939308_5905022047983723438_n.jpg
494 ms
11148635_1060327344010812_703506549646611479_n.png
496 ms
wL6VQj7Ab77.png
32 ms
1JLnMyDN79z.png
32 ms
gm-8CYVMZ_l.png
32 ms
jot.html
36 ms
activeview
31 ms
activeview
41 ms
activeview
45 ms
combined.css
78 ms
smoothDivScroll.css
46 ms
stack_161235.js
69 ms
jquery.min.js
251 ms
stackpile.api-2ece4e50df.js
52 ms
12960110_1686215104963876_1843255941_n.jpg
310 ms
small_share_sprite.png
51 ms
12912297_1549703421990945_1980052548_n.jpg
379 ms
12599275_216723318697825_1690551143_n.jpg
504 ms
12912508_212784082430818_1916990918_n.jpg
537 ms
12677198_1770102143220690_704537476_n.jpg
538 ms
12912751_1777664625801961_1890570939_n.jpg
538 ms
12501535_520966131422058_305983893_n.jpg
588 ms
12940796_247386012267759_1514357481_n.jpg
538 ms
12918451_582998198526529_1727162612_n.jpg
587 ms
collect
23 ms
collect
120 ms
VXcANLwwL5J.js
45 ms
i8XO-4kv8i7.js
44 ms
nr-918.min.js
76 ms
a53393d12f
50 ms
collect
6 ms
ui
44 ms
mathtext.info accessibility score
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
[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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
mathtext.info 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
Browser errors were logged to the console
mathtext.info SEO score
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 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.
mathtext.info
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: