10.4 sec in total
2.2 sec
7.7 sec
493 ms
Click here to check amazing FOOLINE content for Japan. Otherwise, check out these important facts you probably never knew about fooline.net
ビジネスやカルチャーなど、様々なテーマで情報をお届けするコラムサイト。
Visit fooline.netWe analyzed Fooline.net page load time and found that the first response time was 2.2 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fooline.net performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.8 s
15/100
25%
Value10.7 s
7/100
10%
Value2,450 ms
5/100
30%
Value0.046
99/100
15%
Value10.9 s
21/100
10%
2212 ms
27 ms
165 ms
319 ms
342 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 52% of them (49 requests) were addressed to the original Fooline.net, 13% (12 requests) were made to Adm.shinobi.jp and 5% (5 requests) were made to Ssp.advg.jp. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Fooline.net.
Page size can be reduced by 424.7 kB (33%)
1.3 MB
863.3 kB
In fact, the total size of Fooline.net main page is 1.3 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. 40% of websites need less resources to load. Images take 682.1 kB which makes up the majority of the site volume.
Potential reduce by 41.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 41.5 kB or 82% of the original size.
Potential reduce by 0 B
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. FOOLINE images are well optimized though.
Potential reduce by 257.9 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 257.9 kB or 64% of the original size.
Potential reduce by 125.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. Fooline.net needs all CSS files to be minified and compressed as it can save up to 125.3 kB or 83% of the original size.
Number of requests can be reduced by 53 (60%)
88
35
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FOOLINE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
fooline.net
2212 ms
analytics.js
27 ms
wp-emoji-release.min.js
165 ms
crayon.min.css
319 ms
classic.css
342 ms
monaco.css
343 ms
styles.css
343 ms
style.css
511 ms
responsive.css
368 ms
font-awesome.min.css
479 ms
wpp.css
501 ms
amazonjs.css
520 ms
jquery.js
686 ms
jquery-migrate.min.js
552 ms
crayon.min.js
640 ms
jquery.flexslider.min.js
663 ms
53b197b0dbf6a512cfa14852142a0662
361 ms
a1438d250e4c393b1a4d32d0b3a41baa
377 ms
ecd4941c0c58d0b130e6a3b25f97ce5a
390 ms
jquery.form.min.js
808 ms
scripts.js
681 ms
jquery.jplayer.min.js
808 ms
scripts.js
808 ms
wp-embed.min.js
832 ms
collect
27 ms
rogo_fooline.png
247 ms
s-right-s2.png
248 ms
s-left.png
248 ms
5865597031_a06a479a29_b-720x340.jpg
560 ms
12982798014_f4daefb4ce_k-520x245.jpg
543 ms
3040249249_343516df2e_b-520x245.jpg
414 ms
2066176012_71c999d672_b-520x245.jpg
509 ms
182641756_094e20520f_b-520x245.jpg
514 ms
160309634_12b5b2b320_b-520x245.jpg
510 ms
3816549890_b33916a246_b-520x245.jpg
585 ms
6141737522_a2af93c854_b-520x245.jpg
847 ms
8274728646_555f9eab3a_k-520x245.jpg
682 ms
9935521594_d975defc80_k-520x245.jpg
852 ms
4941906229_3fd7acab46_z-520x245.jpg
701 ms
1646-featured-100x80.jpg
767 ms
2463-featured-100x80.jpg
743 ms
3225-featured-100x80.jpg
882 ms
643-featured-100x80.jpg
870 ms
3617-featured-100x80.jpg
913 ms
2095-featured-100x80.jpg
950 ms
488-featured-100x80.jpg
1013 ms
2534-featured-100x80.jpg
1019 ms
2283-featured-100x80.jpg
1028 ms
3449-featured-100x80.jpg
1058 ms
8197458470_a229ff3608_b-520x245.jpg
1226 ms
8231575696_2339be0243_k-520x245.jpg
1131 ms
6995721238_3613e0876e_b-520x245.jpg
1359 ms
3567598296_f1d02b4b03_b-520x245.jpg
1359 ms
fontawesome-webfont.woff
1265 ms
1.0.1.js
388 ms
1.0.0.js
195 ms
sync
180 ms
53b197b0dbf6a512cfa14852142a0662
292 ms
a1438d250e4c393b1a4d32d0b3a41baa
298 ms
ecd4941c0c58d0b130e6a3b25f97ce5a
338 ms
sync
315 ms
sync
410 ms
push_sync
300 ms
js1
560 ms
ib
194 ms
ib
197 ms
js1
531 ms
ib
181 ms
cookiesync
310 ms
sync
217 ms
1.1.0.js
195 ms
receive_sync
150 ms
js
508 ms
js
536 ms
js
509 ms
jstag
11 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456891555323
300 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456891555325
307 ms
acj
13 ms
ri
6 ms
imp
306 ms
sync
161 ms
ads.js
23 ms
adcomp_pc.js
11 ms
sspcore_spot.js
29 ms
ssp_spot.ashx
295 ms
cs
164 ms
adcore.js
27 ms
adcore_pc.js
41 ms
adcore_pc_inline.js
46 ms
ad_spot.aspx
351 ms
style.css
667 ms
ad_creative.ashx
150 ms
receive
189 ms
fooline.net 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
fooline.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fooline.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 doesn't use 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 Fooline.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 Fooline.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.
fooline.net
Open Graph description is not detected on the main page of FOOLINE. 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: