7 sec in total
1.4 sec
5.3 sec
299 ms
Visit wofs.jp now to see the best up-to-date Wofs content for Japan and also check out these interesting facts you probably never knew about wofs.jp
風水グランドマスターリリアン・トゥーが提案する「ワールド・オブ・風水ジャパン(WOFS JAPAN)」公式サイトです。金運、仕事運、インテリア、人相学、相性占いなどライフスタイルにあわせた風水情報をお届けします。
Visit wofs.jpWe analyzed Wofs.jp page load time and found that the first response time was 1.4 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
wofs.jp performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.6 s
34/100
25%
Value6.5 s
39/100
10%
Value510 ms
57/100
30%
Value0.416
23/100
15%
Value5.9 s
66/100
10%
1429 ms
539 ms
368 ms
1263 ms
545 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 77% of them (65 requests) were addressed to the original Wofs.jp, 12% (10 requests) were made to Fsmegamall.jp and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Wofs.jp.
Page size can be reduced by 243.3 kB (43%)
572.3 kB
329.1 kB
In fact, the total size of Wofs.jp main page is 572.3 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. 30% of websites need less resources to load. Javascripts take 274.2 kB which makes up the majority of the site volume.
Potential reduce by 36.3 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 36.3 kB or 77% of the original size.
Potential reduce by 22.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. Wofs images are well optimized though.
Potential reduce by 172.5 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 172.5 kB or 63% of the original size.
Potential reduce by 11.8 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. Wofs.jp needs all CSS files to be minified and compressed as it can save up to 11.8 kB or 79% of the original size.
Number of requests can be reduced by 30 (36%)
83
53
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wofs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.wofs.jp
1429 ms
style.css
539 ms
wofs.js
368 ms
jquery-1.5.min.js
1263 ms
smoothscroll.js
545 ms
widget.css
385 ms
q-a-plus.css
552 ms
styles.css
582 ms
wpp.css
537 ms
jquery.js
1449 ms
jquery-migrate.min.js
733 ms
platform.js
91 ms
q-a-plus.js
194 ms
jquery.form.min.js
599 ms
scripts.js
699 ms
wp-embed.min.js
385 ms
wp-emoji-release.min.js
762 ms
sdk.js
160 ms
1.jpg
1091 ms
2.jpg
1108 ms
3.jpg
939 ms
4.jpg
1135 ms
5.jpg
1116 ms
6.jpg
1233 ms
7.jpg
1264 ms
8.jpg
1284 ms
9.jpg
1293 ms
10.jpg
1316 ms
topbnr_bg2.gif
202 ms
topbnr_bg1.gif
189 ms
topbnr_bg3.gif
201 ms
logo.jpg
396 ms
topbnr_bg4.jpg
388 ms
navigation.gif
722 ms
banner_top_blank.jpg
396 ms
160226_01staircase-100x100.jpg
395 ms
2016_horo_thumb.jpg
574 ms
thumb_fs2016.jpg
587 ms
ltbirdsflying3-100x100.png
938 ms
flag-100x100.jpg
579 ms
FlyingStar_feb2016_thumb.jpg
780 ms
thumb_chy.jpg
1116 ms
160118_01-100x100.jpg
942 ms
FlyingStar_apr2015_thumb-100x100.jpg
777 ms
ltclouds-100x100.png
1083 ms
559-featured-30x30.jpg
969 ms
378-featured-30x30.jpg
974 ms
1953-featured-30x30.jpg
1122 ms
no_thumb.jpg
1127 ms
156-featured-30x30.jpg
1160 ms
399-featured-30x30.jpg
1168 ms
540-featured-30x30.jpg
1264 ms
1911-featured-30x30.jpg
1298 ms
1903-featured-30x30.jpg
1305 ms
415-featured-30x30.jpg
1310 ms
fs_tipoftheday.jpg
1352 ms
fs_horoscope.jpg
1361 ms
fs_kua.jpg
1445 ms
fs_flystar.jpg
1482 ms
fs_fourpillars.jpg
1489 ms
fs_chihoroscope.jpg
1493 ms
fs_compatibility.jpg
1542 ms
fs_gooddays.jpg
1545 ms
widgets.js
78 ms
ga.js
27 ms
__utm.gif
14 ms
__utm.gif
10 ms
55 ms
xd_arbiter.php
140 ms
xd_arbiter.php
306 ms
intsites_top.gif
1445 ms
wofslogo.jpg
1651 ms
intsites_btm.gif
1482 ms
subnavi_bg.gif
1298 ms
search_bg.gif
1533 ms
subnavi_bg3.gif
1362 ms
subnavi_category_head.gif
1420 ms
subnavi_bg2.gif
1372 ms
subnavi_category_middle.gif
1296 ms
subnavi_bottom.gif
1371 ms
tit_articlestoday.jpg
1413 ms
fs_tit.gif
1315 ms
intsites_cnt.gif
1271 ms
footer_bg.gif
1275 ms
wofs.jp 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
Buttons do not have an accessible name
Links do not have a discernible name
wofs.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
wofs.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Wofs.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 Wofs.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.
wofs.jp
Open Graph description is not detected on the main page of Wofs. 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: