6.1 sec in total
1.4 sec
4.3 sec
423 ms
Welcome to frekul.com homepage info - get ready to check Frekul best content for Japan right away, or after learning these important things about frekul.com
Frekulは、あなたの音楽活動をサポートする「バーチャル・プロダクション」です。世界中の音楽サービスに配信する、レコード会社や音楽事務所にアピールする、全国のカラオケに配信する、などの機能をご提供しています。
Visit frekul.comWe analyzed Frekul.com page load time and found that the first response time was 1.4 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
frekul.com performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value15.4 s
0/100
25%
Value8.9 s
15/100
10%
Value560 ms
52/100
30%
Value0.001
100/100
15%
Value9.0 s
33/100
10%
1426 ms
350 ms
721 ms
370 ms
953 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 48% of them (62 requests) were addressed to the original Frekul.com, 11% (14 requests) were made to Scontent.xx.fbcdn.net and 11% (14 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Frekul.com.
Page size can be reduced by 278.1 kB (33%)
832.9 kB
554.8 kB
In fact, the total size of Frekul.com main page is 832.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 476.1 kB which makes up the majority of the site volume.
Potential reduce by 38.9 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 38.9 kB or 75% of the original size.
Potential reduce by 30.0 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. Frekul images are well optimized though.
Potential reduce by 127.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 127.9 kB or 63% of the original size.
Potential reduce by 81.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. Frekul.com needs all CSS files to be minified and compressed as it can save up to 81.3 kB or 80% of the original size.
Number of requests can be reduced by 54 (43%)
127
73
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frekul. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
frekul.com
1426 ms
default.css
350 ms
common.css
721 ms
jquery.jgrowl.css
370 ms
pages.css
953 ms
jquery-1.7.2.min.js
1034 ms
rollover.js
355 ms
jquery.jgrowl.js
384 ms
function.js
519 ms
jquery.activity-indicator-1.0.0.min.js
527 ms
smartRollover.js
566 ms
top_mini.css
693 ms
over_parent.css
700 ms
jquery.jplayer.limit.min.js
907 ms
audio_player.js
748 ms
bookmark_button.js
362 ms
jquery.vticker.min.js
697 ms
button-only@2x.png
195 ms
logo_frekul.png
188 ms
about_frekul_bt.png
206 ms
input4.gif
188 ms
search_bt.png
195 ms
navi_line.png
196 ms
top_photo.jpg
352 ms
frekul_top_logo.png
352 ms
top_listener.png
523 ms
top_artist.png
362 ms
for_listener.png
551 ms
down_bt.png
403 ms
loading_alpha.gif
524 ms
banner_pc_top.jpg
790 ms
talk_session.jpg
791 ms
thumb.php
790 ms
thumb.php
805 ms
thumb.php
805 ms
thumb.php
804 ms
thumb.php
1028 ms
thumb.php
1020 ms
thumb.php
1024 ms
thumb.php
1075 ms
thumb.php
1051 ms
thumb.php
1081 ms
thumb.php
1305 ms
thumb.php
1265 ms
more_link_bt.png
1219 ms
tunecore.jpg
1225 ms
karatetsu.jpg
1248 ms
report.jpg
1265 ms
broadcast.jpg
1430 ms
pertnership.jpg
1427 ms
footer.png
1430 ms
footer_logo.png
1444 ms
widgets.js
128 ms
top_photo_bg.png
1439 ms
228 ms
player_btm.png
1542 ms
a2da36a5-14a5-4aa0-bbd5-1c2a8fe8b243.js
211 ms
all.js
161 ms
ga.js
12 ms
__utm.gif
17 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
126 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
158 ms
likebox.php
917 ms
dot-metrix.p.js
1393 ms
play_bt.png
1414 ms
pause_bt.png
1408 ms
arrow.png
1429 ms
news_bg_top.png
1434 ms
reset.css
13 ms
entry-button.css
12 ms
150 ms
xd_arbiter.php
149 ms
xd_arbiter.php
274 ms
bbtn-s_v3.png
5 ms
syndication
98 ms
292149715519275008
275 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
45 ms
news_bg_bottom.png
1302 ms
ttl_bg_short.png
1401 ms
bg.png
1414 ms
top_listener_on.png
1396 ms
top_artist_on.png
1287 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
27 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
157 ms
C0ke_1CR_normal.jpg
145 ms
default_profile_4_normal.png
199 ms
47-t2lyF_normal.jpg
195 ms
9o0k7-0__normal.jpg
198 ms
W44NqETZ_normal.jpg
209 ms
XUzN6C6c_normal.jpeg
261 ms
Pd5m6Hbt_normal.jpeg
202 ms
uEIfTV4M_normal.jpg
202 ms
dzPrjU0y_normal.png
315 ms
ELlmBEhM_normal.jpg
202 ms
sp2006_normal.jpg
257 ms
moonbow1_normal.png
202 ms
KjFp0y5-_normal.jpg
230 ms
aedc0c2bafd3f2a75d718345869c1a2e_normal.jpeg
266 ms
dFv9dINj_normal.jpg
203 ms
hDvwL1_H7g-.css
175 ms
56WNbrUYLbL.css
219 ms
q68gy-v_YMF.js
305 ms
FJmpeSpHpjS.js
372 ms
0wM5s1Khldu.js
292 ms
1bNoFZUdlYZ.js
299 ms
jot.html
31 ms
582321_198187190326228_1079600134_n.jpg
171 ms
226765_198171360327811_1048715487_n.jpg
206 ms
1017059_568417306534575_1325070465_n.jpg
247 ms
11888066_10152935509511114_5515081838498004630_n.jpg
289 ms
1929866_957012224379648_2058427811743251907_n.jpg
286 ms
12743603_1139845969361794_5792160036207924440_n.jpg
289 ms
10525734_792854224194456_7687728907881784216_n.jpg
290 ms
12190887_555036654647330_4954278059252495683_n.jpg
290 ms
248863_103706063055869_2258198_n.jpg
290 ms
10711019_909746922382610_1970832071826037282_n.jpg
325 ms
11667521_10206582578350445_3829606614984460034_n.jpg
326 ms
10354686_10150004552801856_220367501106153455_n.jpg
325 ms
11115603_971763972876184_7601007826626426661_n.jpg
326 ms
68219_455637364474196_369435455_n.jpg
326 ms
wL6VQj7Ab77.png
55 ms
s7jcwEQH7Sx.png
56 ms
I6-MnjEovm5.js
42 ms
pQrUxxo5oQp.js
81 ms
track
237 ms
track
161 ms
xd_arbiter.php
85 ms
like.php
175 ms
frekul.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
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.
frekul.com 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
frekul.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Frekul.com 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 Frekul.com 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.
frekul.com
Open Graph description is not detected on the main page of Frekul. 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: