6.5 sec in total
1.4 sec
4.6 sec
557 ms
Visit fun-run.tokyo now to see the best up-to-date Fun Run content for Japan and also check out these interesting facts you probably never knew about fun-run.tokyo
迷えるランナーを救うランニングポータルサイトです。ランニングを始めたい。サブ3したい。ウルトラマラソン完走したい。トレイル走ってみたい。と思ったら読むサイトです。
Visit fun-run.tokyoWe analyzed Fun-run.tokyo page load time and found that the first response time was 1.4 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fun-run.tokyo performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value9.4 s
1/100
25%
Value6.0 s
46/100
10%
Value880 ms
32/100
30%
Value1.258
1/100
15%
Value14.9 s
8/100
10%
1350 ms
324 ms
333 ms
368 ms
25 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 89% of them (73 requests) were addressed to the original Fun-run.tokyo, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Fun-run.tokyo.
Page size can be reduced by 130.6 kB (7%)
1.9 MB
1.7 MB
In fact, the total size of Fun-run.tokyo main page is 1.9 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. 55% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 55.8 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 35.2 kB, which is 56% 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 55.8 kB or 88% of the original size.
Potential reduce by 56.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. Fun Run images are well optimized though.
Potential reduce by 50 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 17.9 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. Fun-run.tokyo needs all CSS files to be minified and compressed as it can save up to 17.9 kB or 83% of the original size.
Number of requests can be reduced by 7 (9%)
79
72
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fun Run. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
fun-run.tokyo
1350 ms
reset.css
324 ms
common.css
333 ms
flexslider.css
368 ms
css
25 ms
jquery-1.6.4.min.js
6 ms
scrolTop.js
342 ms
jquery.min.js
26 ms
analytics.js
94 ms
commonM.css
191 ms
sdk.js
107 ms
headerwhite.gif
944 ms
home_off.gif
168 ms
profile_off.gif
174 ms
blog_off.gif
271 ms
training_off.gif
336 ms
race_off.gif
335 ms
racemanegement_off.gif
342 ms
item_off.gif
345 ms
runners_off.gif
447 ms
recovery_off.gif
496 ms
sitemap_off.gif
501 ms
saroma1.jpg
680 ms
catapi.jpg
705 ms
pacer.jpg
965 ms
pacer2.jpg
1129 ms
tanzawa1.jpg
993 ms
tanzawa2.jpg
1030 ms
tanzawa3.jpg
1041 ms
tanzawa4.jpg
1272 ms
tanzawa5.jpg
1319 ms
tanzawa6.jpg
1312 ms
tanzawataki.jpg
1377 ms
gaien.jpg
1232 ms
fuji.jpg
1446 ms
tokyom2.jpg
1407 ms
kaidan.jpg
1453 ms
oda.jpg
1474 ms
akaaokuro.jpg
1674 ms
athletune.jpg
1721 ms
kuhu1.jpg
1581 ms
kuhu3.jpg
1764 ms
hotjel.jpg
1617 ms
ks.jpg
1639 ms
hydrooil.jpg
1755 ms
wear.jpg
1805 ms
collect
37 ms
95 ms
xd_arbiter.php
42 ms
xd_arbiter.php
58 ms
rlsocks.jpg
1719 ms
glass.jpg
1876 ms
hasetune.jpg
1733 ms
hasetune3.jpg
1671 ms
hasetune2.jpg
1759 ms
hasetune4.jpg
1800 ms
simanto.jpg
1639 ms
simanto3.jpg
1739 ms
team.jpg
1670 ms
dns.jpg
1646 ms
medarist.jpg
1717 ms
musashi.jpg
1573 ms
purote.jpg
1549 ms
soy.jpg
1518 ms
water.jpg
1335 ms
reboku.jpg
1317 ms
renboost.jpg
1530 ms
rensen.jpg
1386 ms
rensen2.jpg
1294 ms
sen.jpg
1241 ms
boxback.png
1221 ms
athletune.jpg
1437 ms
hasetsune.jpg
1450 ms
oda.jpg
1251 ms
tsukuba.jpg
1231 ms
garmin.jpg
1364 ms
shinetsu.jpg
1280 ms
kiden.jpg
1326 ms
kouteisa.jpg
1223 ms
care.jpg
1299 ms
toTOp.gif
1276 ms
commonS.css
187 ms
fun-run.tokyo 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
Links do not have a discernible name
fun-run.tokyo 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
fun-run.tokyo 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 Fun-run.tokyo 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 Fun-run.tokyo 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.
fun-run.tokyo
Open Graph description is not detected on the main page of Fun Run. 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: