4.7 sec in total
512 ms
4 sec
204 ms
Click here to check amazing Whereabouts content. Otherwise, check out these important facts you probably never knew about whereabouts.jp
自己成長、自信を取り戻すためのメンタルトレーニング。人間関係、自分の性格に悩む人に対応。発達障害スキルトレーニングやペアレントトレーニング、認知症予防のメニューなど個別メニュー作成が可能です。
Visit whereabouts.jpWe analyzed Whereabouts.jp page load time and found that the first response time was 512 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
whereabouts.jp performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value7.1 s
5/100
25%
Value10.8 s
6/100
10%
Value1,110 ms
23/100
30%
Value0.428
22/100
15%
Value15.2 s
7/100
10%
512 ms
839 ms
75 ms
325 ms
486 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 64% of them (50 requests) were addressed to the original Whereabouts.jp, 15% (12 requests) were made to Static.xx.fbcdn.net and 4% (3 requests) were made to Media.mil.movie. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Whereabouts.jp.
Page size can be reduced by 241.0 kB (40%)
607.2 kB
366.3 kB
In fact, the total size of Whereabouts.jp main page is 607.2 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. 60% of websites need less resources to load. Javascripts take 264.2 kB which makes up the majority of the site volume.
Potential reduce by 25.1 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 25.1 kB or 71% of the original size.
Potential reduce by 2.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. Whereabouts images are well optimized though.
Potential reduce by 169.1 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 169.1 kB or 64% of the original size.
Potential reduce by 44.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. Whereabouts.jp needs all CSS files to be minified and compressed as it can save up to 44.6 kB or 84% of the original size.
Number of requests can be reduced by 42 (58%)
73
31
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whereabouts. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
whereabouts.jp
512 ms
whereabouts.jp
839 ms
js
75 ms
import.css
325 ms
lightbox.css
486 ms
main.js
490 ms
smoothscroll.js
489 ms
ddsmoothmenu.js
493 ms
jquery.min.js
875 ms
analyticstracking.js
531 ms
jquery-1.7.2.min.js
1131 ms
jquery-ui-1.8.18.custom.min.js
493 ms
jquery.smooth-scroll.min.js
492 ms
lightbox.js
497 ms
base.css
383 ms
layout.css
654 ms
analytics.js
48 ms
bg.gif
165 ms
logo.jpg
165 ms
header_tel.jpg
176 ms
header_link.gif
177 ms
header_home_off.gif
164 ms
header_inq_off.gif
332 ms
header_sittemap_off.gif
333 ms
top_catch_new.jpg
821 ms
contents_bg.gif
351 ms
itsuaki.jpg
706 ms
inq_area_bg.gif
459 ms
inq_bt_off.gif
574 ms
mm_bg.jpg
574 ms
bnn_link_off.gif
575 ms
mobile_site_url.gif
616 ms
mobile_site_qr.gif
653 ms
whereabouts_info_add.gif
657 ms
whereabouts_info_tel.gif
701 ms
006.jpg
777 ms
001.png
816 ms
002.png
820 ms
003.png
875 ms
004.png
882 ms
credit_s.png
938 ms
news_ico.gif
978 ms
news_list.gif
984 ms
sdk.js
55 ms
mobile_site_h.gif
961 ms
whereabouts_info.gif
1027 ms
879 ms
top_area01.gif
1033 ms
top_area01_h2.gif
1073 ms
version
884 ms
footer_bg.gif
1106 ms
footer_inner_bg.gif
1113 ms
collect
34 ms
sdk.js
5 ms
39 ms
collect
28 ms
ga-audiences
29 ms
close.png
1070 ms
loading.gif
820 ms
close.png
900 ms
page.php
103 ms
LO_ZbPzgR8d.css
22 ms
XVfyC-hY3iC.js
31 ms
4vv_Lf70fZS.js
22 ms
Y4lQlibYsna.js
25 ms
4aFcRp6-srT.js
75 ms
8O2J-mJIMh1.js
26 ms
Mgao39tvtRW.js
73 ms
mtuC5ESzCwN.js
29 ms
HYZXJ6lnRqE.js
71 ms
p55HfXW__mM.js
28 ms
300593470_435528995266316_7465804020618391341_n.jpg
140 ms
mFWyxjCB51c.js
12 ms
300783805_435528991932983_1540558447086693565_n.jpg
150 ms
UXtr_j2Fwe-.png
10 ms
2184f7206de09408d3375c49a6a15e49.png
885 ms
mil_player_promise.js
904 ms
mil_loader.js
892 ms
whereabouts.jp 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
whereabouts.jp 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
Browser errors were logged to the console
Page has valid source maps
whereabouts.jp 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
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whereabouts.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 Whereabouts.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
whereabouts.jp
Open Graph description is not detected on the main page of Whereabouts. 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: