9.9 sec in total
3.7 sec
6 sec
181 ms
Click here to check amazing FUNA content for Japan. Otherwise, check out these important facts you probably never knew about funa.in.net
医学クイズ
Visit funa.in.netWe analyzed Funa.in.net page load time and found that the first response time was 3.7 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
funa.in.net performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value6.7 s
8/100
25%
Value11.4 s
5/100
10%
Value650 ms
46/100
30%
Value0
100/100
15%
Value14.1 s
9/100
10%
3749 ms
315 ms
341 ms
846 ms
509 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 38% of them (37 requests) were addressed to the original Funa.in.net, 12% (12 requests) were made to Pbs.twimg.com and 8% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Funa.in.net.
Page size can be reduced by 654.4 kB (64%)
1.0 MB
375.0 kB
In fact, the total size of Funa.in.net main page is 1.0 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. 65% of websites need less resources to load. CSS take 421.8 kB which makes up the majority of the site volume.
Potential reduce by 37.5 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 37.5 kB or 75% of the original size.
Potential reduce by 41.2 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, FUNA needs image optimization as it can save up to 41.2 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 217.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 217.2 kB or 69% of the original size.
Potential reduce by 358.4 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. Funa.in.net needs all CSS files to be minified and compressed as it can save up to 358.4 kB or 85% of the original size.
Number of requests can be reduced by 55 (57%)
96
41
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FUNA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
funa.in.net
3749 ms
common.css
315 ms
layout.css
341 ms
design.css
846 ms
mobile.css
509 ms
mobile_layout.css
344 ms
advanced.css
349 ms
font-awesome.min.css
619 ms
bootstrap.css
1284 ms
front.css
869 ms
frontend.css
364 ms
amazonjs.css
526 ms
jetpack.css
712 ms
jquery.js
1195 ms
jquery-migrate.min.js
773 ms
bootstrap.min.js
1024 ms
front.js
894 ms
chosen.jquery.min.js
1126 ms
line-button.js
499 ms
jquery.form.min.js
1035 ms
devicepx-jetpack.js
6 ms
gprofiles.js
54 ms
wpgroho.js
1061 ms
utility.js
1188 ms
socialButton.js
1207 ms
wp-slimstat.min.js
11 ms
wp-embed.min.js
1234 ms
e-201611.js
5 ms
wp-emoji-release.min.js
632 ms
css
64 ms
feedly-follow-rectangle-volume-small_2x.png
18 ms
logo_rectangle320-%E3%82%B3%E3%83%94%E3%83%BCnss.png
203 ms
bg-menu.png
203 ms
bg-conts-h.gif
174 ms
R%E3%81%BF%E3%82%93%E3%82%B3%E3%83%AC%EF%BC%81110small.png
188 ms
%E9%81%8E%E5%8E%BB%E5%95%8F%EF%BC%A4%EF%BC%A2.png
201 ms
wordpress-logo-hoz-rgb.png
187 ms
logo_rectangle320-%E3%82%B3%E3%83%94%E3%83%BCs.png
335 ms
sitelogo_40.png
361 ms
widgets.js
14 ms
icon-arrow_r_gray.png
331 ms
icon-arrow02.png
334 ms
icon-arrow01.png
322 ms
bg-pagetop.png
335 ms
hovercard.css
51 ms
services.css
69 ms
button-only@2x.png
334 ms
bookmark_button.js
354 ms
platform.js
92 ms
all.js
17 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
63 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
91 ms
g.gif
51 ms
263 ms
xd_arbiter.php
38 ms
xd_arbiter.php
71 ms
cb=gapi.loaded_0
14 ms
cb=gapi.loaded_1
28 ms
fastbutton
117 ms
syndication
130 ms
495183274931539969
165 ms
postmessageRelay
50 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
20 ms
3193398744-postmessagerelay.js
37 ms
rpc:shindig_random.js
35 ms
cb=gapi.loaded_0
23 ms
cb=gapi.loaded_1
20 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
40 ms
cb=gapi.loaded_0
17 ms
print.css
178 ms
proxy.jpg
71 ms
1f4a6.png
45 ms
proxy.jpg
27 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
6 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
7 ms
260455_1087329149_normal.jpg
57 ms
9R4SOTvq_normal.png
119 ms
Qrwq5vpS_normal.png
177 ms
ETRDXmEG_normal.jpeg
175 ms
rAGTjMW9_normal.jpg
114 ms
DfUm5X7C_normal.jpg
114 ms
6d12dcb1d4621d9f412bb16413a62380_normal.jpeg
240 ms
7E9THF6L_normal.jpg
174 ms
UsyIv5vj_normal.jpg
180 ms
ZfX3mp1i_normal.jpg
175 ms
S3zQcxI6_normal.jpg
236 ms
KzMn8YPR_normal.jpg
176 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
47 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
95 ms
260 ms
proxy.jpg
45 ms
proxy.jpg
2 ms
reset.css
8 ms
entry-button.css
9 ms
bbtn-s_v3.png
4 ms
like.php
192 ms
jot.html
3 ms
LVx-xkvaJ0b.png
23 ms
funa.in.net accessibility score
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
Form elements do not have associated labels
funa.in.net 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
funa.in.net SEO score
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funa.in.net 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 Funa.in.net 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.
funa.in.net
Open Graph data is detected on the main page of FUNA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: