4.9 sec in total
459 ms
4.1 sec
336 ms
Welcome to geo-mobile.jp homepage info - get ready to check Geo Mobile best content for Japan right away, or after learning these important things about geo-mobile.jp
格安スマホを買うなら全国にサポート店のある「ゲオモバイル」!中古スマホ×格安SIMで今よりも安くスマホを使いましょう!Softbank、docomo、au、など常時数千台の品揃え。もちろん安心の保証も行なっています。格安スマホ、中古スマホ、スマホ買取のことならゲオモバイル!
Visit geo-mobile.jpWe analyzed Geo-mobile.jp page load time and found that the first response time was 459 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
geo-mobile.jp performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value16.1 s
0/100
25%
Value5.9 s
49/100
10%
Value520 ms
57/100
30%
Value0.03
100/100
15%
Value11.0 s
21/100
10%
459 ms
582 ms
293 ms
296 ms
296 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 84% of them (53 requests) were addressed to the original Geo-mobile.jp, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Geo-mobile.jp.
Page size can be reduced by 711.9 kB (28%)
2.5 MB
1.8 MB
In fact, the total size of Geo-mobile.jp main page is 2.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. 35% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 19.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 19.0 kB or 76% of the original size.
Potential reduce by 370.4 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. Obviously, Geo Mobile needs image optimization as it can save up to 370.4 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 263.8 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 263.8 kB or 69% of the original size.
Potential reduce by 58.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. Geo-mobile.jp needs all CSS files to be minified and compressed as it can save up to 58.7 kB or 83% of the original size.
Number of requests can be reduced by 24 (39%)
61
37
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geo Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
geo-mobile.jp
459 ms
common.css
582 ms
second.css
293 ms
gm.css
296 ms
top.css
296 ms
shadowbox.css
311 ms
shadowbox.js
932 ms
jquery-1.11.1.min.js
736 ms
jquery-migrate-1.2.1.min.js
5 ms
jquery.bxslider.min.js
445 ms
textcut.js
302 ms
jquery.easing.1.3.js
326 ms
sly.min.js
595 ms
main_run.js
482 ms
gm.js
588 ms
top_items.js
591 ms
geo_logo.png
154 ms
png_file-s4be5f85eca.png
587 ms
commonnavi_bg.jpg
153 ms
sprite.png
466 ms
ico_new_square.png
163 ms
top_keyvisual.png
587 ms
top_keyvisual_btn.png
299 ms
top_point01_text.png
589 ms
top_point01_btn.png
316 ms
top_point02_text.png
738 ms
top_point02_btn.png
472 ms
top_point03_text.png
624 ms
top_point03_btn.png
627 ms
appli_bnr.jpg
735 ms
twitter_bnr.jpg
878 ms
axol_bnr.jpg
881 ms
adopt_bnr.jpg
781 ms
bg_sidenav.jpg
783 ms
bg_sidemenu_btn_off.png
884 ms
leftGeoMobileMovieIcon.jpg
883 ms
commonnavi_bg_bottom.jpg
936 ms
bottomtitbar.png
939 ms
bottomsubtitbar.png
1024 ms
btn_totop.png
1028 ms
analytics.js
28 ms
tag.js
203 ms
akiba_renewal_127x49.jpg
1088 ms
akiba_renewal_700x241.jpg
1095 ms
geo-mobile_201601cp_127x49.jpg
1157 ms
geo-mobile_201601cp_700x241.jpg
1475 ms
netkaitori_127x49.jpg
1227 ms
netkaitori_700x241.jpg
1527 ms
OCN_127x49.jpg
1379 ms
OCN700x241.jpg
1395 ms
UQ_127x49.jpg
1467 ms
UQ_700x241.jpg
1672 ms
web_yoyaku_thumb.0910.jpg
1671 ms
web_yoyaku.0910.jpg
1691 ms
linkid.js
12 ms
collect
12 ms
collect
63 ms
icon_bx-cont-dir_prev.png
1567 ms
icon_bx-cont-dir_next.png
1574 ms
tag
5 ms
conversion_async.js
34 ms
32 ms
36 ms
geo-mobile.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
Image elements do not have [alt] attributes
Links do not have a discernible name
geo-mobile.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
geo-mobile.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geo-mobile.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 Geo-mobile.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.
geo-mobile.jp
Open Graph data is detected on the main page of Geo Mobile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: