10.9 sec in total
1.9 sec
7.6 sec
1.4 sec
Visit hokomama.com now to see the best up-to-date Hokomama content for Japan and also check out these interesting facts you probably never knew about hokomama.com
主人が仕事をやめました・・・∑(; ̄□ ̄A介護問題抱え、二人で始めたせどり・輸入・輸出の転売ビジネス!今では時間もお金もほっこり生活♪家族の時間が充実しています☆会社がなくたって生きて行けるスキルを身につけて本当の自由を手にいれませんか?
Visit hokomama.comWe analyzed Hokomama.com page load time and found that the first response time was 1.9 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hokomama.com performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value9.9 s
0/100
25%
Value8.8 s
15/100
10%
Value430 ms
65/100
30%
Value0.002
100/100
15%
Value11.3 s
19/100
10%
1894 ms
854 ms
519 ms
864 ms
6 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 45% of them (70 requests) were addressed to the original Hokomama.com, 7% (11 requests) were made to Ecx.images-amazon.com and 6% (9 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Hokomama.com.
Page size can be reduced by 469.1 kB (31%)
1.5 MB
1.1 MB
In fact, the total size of Hokomama.com main page is 1.5 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. 70% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 98.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 98.3 kB or 82% of the original size.
Potential reduce by 91.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. Hokomama images are well optimized though.
Potential reduce by 132.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 132.9 kB or 65% of the original size.
Potential reduce by 146.2 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. Hokomama.com needs all CSS files to be minified and compressed as it can save up to 146.2 kB or 86% of the original size.
Number of requests can be reduced by 64 (42%)
151
87
The browser has sent 151 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hokomama. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
hokomama.com
1894 ms
style.css
854 ms
pink.css
519 ms
shortcode.css
864 ms
jquery-1.8.1.min.js
6 ms
jquery.min.js
81 ms
smoothscroll.js
511 ms
style.css
372 ms
jetpack.css
1279 ms
jquery.js
1530 ms
jquery-migrate.min.js
912 ms
enhanced-categories.js
844 ms
bookmark_button.js
373 ms
plusone.js
112 ms
devicepx-jetpack.js
56 ms
gprofiles.js
59 ms
wpgroho.js
341 ms
jquery.easing.js
346 ms
dynamic.to.top.min.js
358 ms
wp-embed.min.js
359 ms
e-201609.js
10 ms
wp-emoji-release.min.js
1008 ms
button-only.gif
252 ms
ir
248 ms
02-300x111.png
59 ms
66c19942ab4ba346fdb64ccc04cde3731.jpg
1551 ms
022.png
1073 ms
banner_22.gif
426 ms
tenbai88_31.gif
380 ms
top.gif
523 ms
170x170_03.png
1068 ms
top.gif
525 ms
ir
240 ms
ir
236 ms
ir
241 ms
ir
255 ms
ir
255 ms
back.png
233 ms
g_back.png
239 ms
banner_back.png
371 ms
cropped-ber002.jpg
786 ms
top091602.png
1059 ms
01.jpg
592 ms
02-300x111.png
1061 ms
Screenshot_2016-01-06-13-45-18-200x200.png
1068 ms
03-200x200.jpg
1050 ms
coldsweats02.gif
783 ms
20121213-200x200.jpg
1151 ms
dbad6d1a3f2da1f2b7953d42162d3a95-200x200.jpg
1156 ms
hokogazou-e1369997048811.jpg
1392 ms
note.gif
1112 ms
birthday.gif
1144 ms
up.gif
1186 ms
ran11.jpg
2127 ms
ran01-e1402656266912.jpg
1626 ms
kizi-212x300.jpg
1631 ms
20141012031653-300x177.jpg
1534 ms
20141012031718-300x181.jpg
1368 ms
20131022-big.jpg
2718 ms
c49f18762521695675bad117185fe017.jpg
1733 ms
sign03.gif
1699 ms
beer.gif
1800 ms
catface.gif
1802 ms
email-orange.jpg
1879 ms
hokomama_avatar_1408674581-96x96.jpg
1905 ms
01-150x150.jpg
1970 ms
Screenshot_2016-01-06-13-45-18-150x150.png
2479 ms
03-150x150.jpg
2059 ms
20121213-150x150.jpg
2077 ms
dbad6d1a3f2da1f2b7953d42162d3a95-150x150.jpg
2141 ms
33b659f4cff89fd5007d7b60b38602cd-150x150.jpg
2420 ms
all.js
36 ms
amazon01-150x150.jpg
2216 ms
widgets.js
51 ms
cb=gapi.loaded_0
63 ms
139 ms
276 ms
xd_arbiter.php
78 ms
xd_arbiter.php
129 ms
61LeX0vSsDL._SL250_.jpg
78 ms
51Fx1d4LjnL._SL250_.jpg
72 ms
fuuzin-09-150x150.jpg
2594 ms
61G-R7KtYjL._SL250_.jpg
74 ms
61x9JIQ0TSL._SL250_.jpg
74 ms
61QYr%2B9mSTL._SL250_.jpg
74 ms
sedo02.gif
2088 ms
41V4zFakRoL._SL110_.jpg
52 ms
cb=gapi.loaded_1
40 ms
fastbutton
145 ms
421 ms
osusume01-150x150.gif
2239 ms
postmessageRelay
113 ms
sedoruranku-300x167.jpg
2613 ms
reset.css
30 ms
entry-button.css
30 ms
button-counter.gif
59 ms
cb=gapi.loaded_0
44 ms
cb=gapi.loaded_1
54 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
516 ms
api.js
135 ms
core:rpc:shindig.random:shindig.sha1.js
514 ms
2536007149-postmessagerelay.js
261 ms
fastbutton
213 ms
441 ms
448 ms
449 ms
unnamed.png
2555 ms
cm
405 ms
cm
411 ms
cm
421 ms
cm
413 ms
back1.png
1874 ms
hovercard.css
127 ms
services.css
130 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
134 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
134 ms
fastbutton
198 ms
back2.png
1926 ms
310WbvGP29L._SL100_.jpg
109 ms
283 ms
buy-from-tan.gif
99 ms
41ZyOd7O8WL._SL100_.jpg
98 ms
274 ms
h3.png
1777 ms
41OUw7n3vCL._SL100_.jpg
93 ms
271 ms
clear.png
1837 ms
41fanqqP7aL._SL100_.jpg
86 ms
265 ms
sub_back2.png
1943 ms
sub_back1.png
1927 ms
g.gif
72 ms
223 ms
arrow.png
1950 ms
syndication
243 ms
491796268956401664
285 ms
sr.png
3291 ms
top_btn.png
2019 ms
like.php
172 ms
footer.png
2029 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
111 ms
like.php
183 ms
ex-line.png
3302 ms
like.php
191 ms
like.php
198 ms
like.php
214 ms
rU2ubZ6l1Q5.js
62 ms
LVx-xkvaJ0b.png
71 ms
fb.png
1864 ms
sub_back3.png
1944 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
4 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
9 ms
hokogazou_normal.jpg
96 ms
ex-line1.png
3258 ms
ex-line1.png
1744 ms
jot.html
2 ms
hokomama.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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 IDs are not unique
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
No form fields have multiple labels
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
hokomama.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hokomama.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 Hokomama.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 Hokomama.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.
hokomama.com
Open Graph data is detected on the main page of Hokomama. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: