4.1 sec in total
530 ms
3 sec
585 ms
Click here to check amazing 10 Geo content for Japan. Otherwise, check out these important facts you probably never knew about 10.geo.jp
ジャンボ宝くじの高額当選!西銀座デパートチャンスセンターで購入代行サービス。佐賀県唐津市の宝当神社にて当選祈願代行サービス。
Visit 10.geo.jpWe analyzed 10.geo.jp page load time and found that the first response time was 530 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
10.geo.jp performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value1.2 s
100/100
25%
Value2.1 s
99/100
10%
Value20 ms
100/100
30%
Value0.107
88/100
15%
Value3.5 s
92/100
10%
530 ms
349 ms
405 ms
89 ms
128 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 13% of them (15 requests) were addressed to the original 10.geo.jp, 32% (36 requests) were made to Static.xx.fbcdn.net and 16% (18 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain 10.geo.jp.
Page size can be reduced by 849.7 kB (41%)
2.1 MB
1.2 MB
In fact, the total size of 10.geo.jp main page is 2.1 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 947.6 kB which makes up the majority of the site volume.
Potential reduce by 2.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 2.3 kB or 64% of the original size.
Potential reduce by 38.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. 10 Geo images are well optimized though.
Potential reduce by 603.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 603.5 kB or 69% of the original size.
Potential reduce by 205.7 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. 10.geo.jp needs all CSS files to be minified and compressed as it can save up to 205.7 kB or 83% of the original size.
Number of requests can be reduced by 48 (45%)
107
59
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 10 Geo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
10.geo.jp
530 ms
style.css
349 ms
new.html
405 ms
BE2Gzh7DLYs
89 ms
4M9eScbwZjg
128 ms
pr.pr
859 ms
likebox.php
292 ms
www-embed-player-vflQrT_sR.css
61 ms
www-embed-player.js
89 ms
base.js
153 ms
1eJU4PjErWSV5LNTKFXcze5UHikZLg3viIH581vcHWA.js
70 ms
ad_status.js
72 ms
xYm_UD1pmAz.css
294 ms
TGpOWuX6Pv8.css
361 ms
7kdskVxkCNz.css
431 ms
4bFiQ5zDJys.css
561 ms
kCqR6fITdsR.css
498 ms
xPdT2kQG4vz.css
584 ms
q4ddCsQTBkK.css
571 ms
H-92Cz4DIPN.css
502 ms
_rx8naC75Dy.js
590 ms
x5F9OMjKyLw.js
717 ms
ICDbTSzjQEg.js
601 ms
TTCre3391I0.js
627 ms
njO1TPvGzoR.js
634 ms
b_6HNn_J2BZ.js
634 ms
7cm7D75Y0Sf.js
714 ms
rFmE1g6Dkoz.js
842 ms
336JejShbZp.js
713 ms
W0OV23mIOyO.js
714 ms
hdPYw5PFPz4.js
783 ms
D6JJJzT-tB6.js
781 ms
NPuyGQIfUx-.js
834 ms
JMI5tmJvZMw.js
781 ms
36TdwhIHusi.js
781 ms
DusqSB58d-B.js
832 ms
ZNPAadQNc33.js
864 ms
DKRU1bYTkTw.js
961 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
66 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
92 ms
shab.jpg
662 ms
bg_header.jpg
768 ms
bg_right_title.jpg
385 ms
bg_footer.jpg
815 ms
maps
35 ms
nishiginza1.jpg
1034 ms
gin1.jpg
1036 ms
gin2.jpg
1180 ms
gin3.jpg
1326 ms
2.jpg
1545 ms
1.jpg
1613 ms
999.jpg
1408 ms
3.jpg
1788 ms
embed
498 ms
js
86 ms
init_embed.js
26 ms
common.js
37 ms
map.js
38 ms
google4.png
44 ms
overlay.js
64 ms
util.js
40 ms
onion.js
53 ms
search_impl.js
60 ms
StaticMapService.GetMapImage
437 ms
stats.js
65 ms
ViewportInfoService.GetViewportInfo
176 ms
controls.js
25 ms
transparent.png
187 ms
css
225 ms
entity11.png
176 ms
75917_459027550807101_1840787113_n.jpg
510 ms
405027_458663150843541_1279915434_n.jpg
572 ms
10354686_10150004552801856_220367501106153455_n.jpg
640 ms
11026305_10204405070349566_3609440733810337806_n.jpg
743 ms
1472769_507438332697650_1361392950_n.jpg
728 ms
1426519_753579754772612_7023293319197622936_n.jpg
767 ms
10398972_1722863151270607_3077036147297986977_n.jpg
709 ms
63391_186885684660076_5706091_n.jpg
885 ms
12814688_201839493507477_888340450945675905_n.jpg
707 ms
12734206_556468511178082_5939968861945323854_n.jpg
775 ms
11694816_131171213888011_7488385058820443949_n.jpg
776 ms
12790952_188949928141664_4585218110032820802_n.jpg
795 ms
66471_101215646723255_1819814855_n.jpg
993 ms
12794455_1028384140538103_7350814232076478783_n.jpg
965 ms
12514158_1026456070730910_2118848204_n.jpg
1030 ms
12744611_1026313237411860_956786610821902987_n.jpg
1013 ms
12744447_1026304474079403_5140188870730234255_n.jpg
994 ms
1067344_1025397364170114_381744836_n.jpg
1016 ms
wL6VQj7Ab77.png
148 ms
s7jcwEQH7Sx.png
147 ms
WC6AgLuP72p.png
148 ms
QDwYpIaRyfG.png
147 ms
l5aPruN9xMM.png
147 ms
a-ZN6WoEOje.png
145 ms
mapcnt6.png
111 ms
ViewportInfoService.GetViewportInfo
101 ms
kh
154 ms
tIFXiEZJgab.js
133 ms
Fl1c2TVhCj-.png
100 ms
tmapctrl.png
53 ms
ViewportInfoService.GetViewportInfo
29 ms
vt
150 ms
vt
178 ms
vt
171 ms
vt
149 ms
vt
165 ms
vt
200 ms
vt
248 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
9 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
14 ms
AuthenticationService.Authenticate
31 ms
I6-MnjEovm5.js
69 ms
vlXaquuXMrr.js
134 ms
10.geo.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.
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 valid value for its [lang] attribute.
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.
10.geo.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
General
Impact
Issue
Detected JavaScript libraries
10.geo.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
robots.txt is not valid
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 10.geo.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 10.geo.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.
10.geo.jp
Open Graph description is not detected on the main page of 10 Geo. 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: