7.2 sec in total
2 sec
5 sec
303 ms
Click here to check amazing Phoenix Lounge content. Otherwise, check out these important facts you probably never knew about phoenixlounge.jp
「学び」をキーワードにしたレンタルスペース。子育てにも、仕事にも、健康にも、就活にも役立つ出張カルチャースクール大集合!!
Visit phoenixlounge.jpWe analyzed Phoenixlounge.jp page load time and found that the first response time was 2 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
phoenixlounge.jp performance score
1960 ms
358 ms
523 ms
549 ms
379 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 55% of them (48 requests) were addressed to the original Phoenixlounge.jp, 11% (10 requests) were made to Static.xx.fbcdn.net and 10% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Phoenixlounge.jp.
Page size can be reduced by 686.0 kB (13%)
5.4 MB
4.7 MB
In fact, the total size of Phoenixlounge.jp main page is 5.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. 60% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 41.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. 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.0 kB or 75% of the original size.
Potential reduce by 243.7 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. Phoenix Lounge images are well optimized though.
Potential reduce by 312.7 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 312.7 kB or 69% of the original size.
Potential reduce by 88.6 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. Phoenixlounge.jp needs all CSS files to be minified and compressed as it can save up to 88.6 kB or 82% of the original size.
Number of requests can be reduced by 36 (44%)
82
46
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phoenix Lounge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
phoenixlounge.jp
1960 ms
styles.css
358 ms
gce-style.css
523 ms
jquery.galleryview-3.0-dev-responsive.css
549 ms
mtssb-front.css
379 ms
style.css
964 ms
style-frontpage.css
525 ms
jquery.js
1311 ms
jquery-migrate.min.js
702 ms
jquery-qtip.js
1039 ms
gce-script.js
723 ms
jquery.timers-1.2.js
730 ms
jquery.easing.1.3.js
895 ms
jquery.gview-3.0-dev-responsive.js
1087 ms
frontend.js
915 ms
nivo-slider.js
1068 ms
style-mobile.css
752 ms
ajax.js
618 ms
jquery.form.min.js
679 ms
scripts.js
708 ms
jquery.ui.core.min.js
734 ms
fontfaces.css
330 ms
teragoya_header_icon_phoenixlounge.png
378 ms
pres_chefing_lounge.png
1572 ms
pres_flowyogga_lounge.png
1535 ms
pres_shiatsuin_lounge.png
1671 ms
pres_kougi_lounge.png
732 ms
pres_shuukatsujuku_lounge.png
2113 ms
5f5960e760bada28d45bd66d1259c3a0.png
560 ms
760fca1c6dcd680fe2282517068fb2e4.png
746 ms
f9dc48e83011d693a4aa1d0a3664c31e1.png
1079 ms
Rithmix_phoenixlounge_web2.png
926 ms
c18e9006f120c080dde132e89d8d2f6c1.jpg
1107 ms
unesco_phoenix_icon_web.png
1438 ms
okazaki_phoenix_web_new.png
1286 ms
aoikai_phoenixlounge.png
1467 ms
uemiya_phoenix_web_new.png
1619 ms
yasuda_flowyoga_phoenixlounge_web.png
1648 ms
konaka_phoenix_web.png
1704 ms
eigayawa_icon2.png
1744 ms
miyamoto_ssbt_phoenixlounge_logo.png
2157 ms
comingsoon_phoenix_web.png
1829 ms
embed
128 ms
loading.gif
1836 ms
ubuntu-regular-webfont.woff
1853 ms
DroidSans-webfont.woff
1928 ms
elusive.woff
1989 ms
all.js
119 ms
arrows.png
1922 ms
OpenSans-Light-webfont.woff
1923 ms
likebox.php
364 ms
embed
181 ms
110 ms
xd_arbiter.php
68 ms
xd_arbiter.php
134 ms
3430f64db2448d201eb4b634c52f3bb9embedcompiled_fastui.css
7 ms
3430f64db2448d201eb4b634c52f3bb9embedcompiled__en.js
16 ms
client.js
61 ms
cb=gapi.loaded_0
12 ms
postmessageRelay
34 ms
3193398744-postmessagerelay.js
30 ms
rpc:shindig_random.js
34 ms
bekMD-lCbkm.css
102 ms
sEpAygasRyW.css
126 ms
6bIl72b-rkY.js
167 ms
TkV0upu1GVq.js
202 ms
mn6tHWuLI-Y.js
183 ms
x8BMxYCqTb9.js
181 ms
cb=gapi.loaded_0
16 ms
logo-plus.png
17 ms
googlelogo_color_46x16dp.png
45 ms
proxy.html
55 ms
cb=gapi.loaded_0
19 ms
events
302 ms
601094_190425334414467_1739265247_n.jpg
144 ms
wL6VQj7Ab77.png
37 ms
s7jcwEQH7Sx.png
38 ms
934868_201059903351010_866854621_n.png
123 ms
1013459_532773880225122_4313502439540335445_n.jpg
131 ms
1017161_617937484952162_336856777_n.jpg
107 ms
12743773_1691827784432470_1768858299502256950_n.jpg
254 ms
10931220_765968733481086_65593633557531063_n.jpg
145 ms
12799179_992544637491258_6199543300701249731_n.jpg
126 ms
1395290_865297960168614_2557283992515634832_n.jpg
162 ms
190753_113108058768621_6911361_n.jpg
142 ms
VXcANLwwL5J.js
18 ms
50Trs1RKgUY.js
21 ms
ping
48 ms
phoenixlounge.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phoenixlounge.jp 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 Phoenixlounge.jp 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.
phoenixlounge.jp
Open Graph data is detected on the main page of Phoenix Lounge. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: