Tools & Wizards About Us
geo-mobile.jp screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

geo-mobile.jp

ゲオモバイル｜中古スマホ・中古携帯・格安スマホの販売・買取情報サイト

Page Load Speed

5.7 sec in total

First Response

630 ms

Resources Loaded

4.6 sec

Page Rendered

435 ms

geo-mobile.jp screenshot

About Website

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.jp

Key Findings

We analyzed Geo-mobile.jp page load time and found that the first response time was 630 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

geo-mobile.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value45.7 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value6,950 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

geo-mobile.jp

630 ms

jquery-2.1.0.min.js

581 ms

jquery.bxslider.css

312 ms

default.css

312 ms

common.css

467 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 94% of them (93 requests) were addressed to the original Geo-mobile.jp, 3% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.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 Optimization Overview & Recommendations

Page size can be reduced by 650.3 kB (11%)

Content Size

5.9 MB

After Optimization

5.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Geo-mobile.jp main page is 5.9 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. 55% of websites need less resources to load. Images take 5.7 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 37.2 kB

  • Original 49.4 kB
  • After minification 40.9 kB
  • After compression 12.2 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. This page needs HTML code to be minified as it can gain 8.5 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 37.2 kB or 75% of the original size.

Image Optimization

-8%

Potential reduce by 431.1 kB

  • Original 5.7 MB
  • After minification 5.2 MB

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. Geo Mobile images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 112.9 kB

  • Original 151.7 kB
  • After minification 121.2 kB
  • After compression 38.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 112.9 kB or 74% of the original size.

CSS Optimization

-87%

Potential reduce by 69.0 kB

  • Original 79.3 kB
  • After minification 45.5 kB
  • After compression 10.3 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 69.0 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (32%)

Requests Now

94

After Optimization

64

  • Images
  • JavaScript
  • CSS

The browser has sent 94 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 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

geo-mobile.jp

geo-mobile.jp

630 ms

jquery-2.1.0.min.js

jquery-2.1.0.min.js

581 ms

jquery.bxslider.css

jquery.bxslider.css

312 ms

default.css

default.css

312 ms

common.css

common.css

467 ms

top.css

top.css

469 ms

jquery.bxslider.js

jquery.bxslider.js

314 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

161 ms

common.js

common.js

164 ms

home.js

home.js

315 ms

css

css

37 ms

gtm.js

gtm.js

132 ms

hed_logo.png

hed_logo.png

160 ms

arrow1_r.png

arrow1_r.png

166 ms

nav01.png

nav01.png

158 ms

nav02.png

nav02.png

159 ms

nav03.png

nav03.png

157 ms

nav04.png

nav04.png

153 ms

nav05.png

nav05.png

299 ms

nav07.png

nav07.png

297 ms

bg02.png

bg02.png

310 ms

hed_logo2.png

hed_logo2.png

314 ms

sp_btn_on.png

sp_btn_on.png

312 ms

sp_btn.png

sp_btn.png

314 ms

bg03.png

bg03.png

444 ms

mobilede_text.png

mobilede_text.png

455 ms

uammk70000006plk.png

uammk70000006plk.png

776 ms

PC_kaitori.jpg

PC_kaitori.jpg

637 ms

mobilede_bg01_color.png

mobilede_bg01_color.png

470 ms

buy3_2.svg

buy3_2.svg

624 ms

buy3ura_2.svg

buy3ura_2.svg

733 ms

buy_1_sp.svg

buy_1_sp.svg

610 ms

PC_hanbai.jpg

PC_hanbai.jpg

939 ms

mobilede_bg02_color.png

mobilede_bg02_color.png

767 ms

sell3_2.svg

sell3_2.svg

1253 ms

sell3ura_2.svg

sell3ura_2.svg

942 ms

sell_2_sp.svg

sell_2_sp.svg

879 ms

PC_tempo-sprt.png

PC_tempo-sprt.png

1546 ms

mobilede_bg03_color.png

mobilede_bg03_color.png

931 ms

contract3_2.svg

contract3_2.svg

1027 ms

contract3ura_3.svg

contract3ura_3.svg

1238 ms

contractura_1_sp.svg

contractura_1_sp.svg

1094 ms

hfctgo000005vl39.jpg

hfctgo000005vl39.jpg

1107 ms

hfctgo000005q7yh.png

hfctgo000005q7yh.png

1173 ms

hfctgo0000035wkl.png

hfctgo0000035wkl.png

1250 ms

235x85_bnr_shinkohin.png

235x85_bnr_shinkohin.png

1268 ms

hfctgo000003nmfd.png

hfctgo000003nmfd.png

1317 ms

hfctgo000001cby5.png

hfctgo000001cby5.png

1393 ms

gtm.js

gtm.js

76 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

24 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

34 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

34 ms

news2_bg.jpg

news2_bg.jpg

1579 ms

sub_icon04.png

sub_icon04.png

1263 ms

news2_text2.png

news2_text2.png

1261 ms

news2_text1.png

news2_text1.png

1309 ms

question_bg.png

question_bg.png

1388 ms

question_bg3.png

question_bg3.png

1407 ms

sub_icon01.png

sub_icon01.png

1279 ms

question_bg2.png

question_bg2.png

1315 ms

question_03.png

question_03.png

1396 ms

question_01.png

question_01.png

1395 ms

question_02.png

question_02.png

1415 ms

question_04.png

question_04.png

1420 ms

advantage_bg.jpg

advantage_bg.jpg

1314 ms

sub_icon02.png

sub_icon02.png

1408 ms

arrow3_r.png

arrow3_r.png

1392 ms

advantage_icon02.png

advantage_icon02.png

1260 ms

advantage_icon02_sp.png

advantage_icon02_sp.png

1249 ms

advantage_icon03.png

advantage_icon03.png

1254 ms

advantage_icon03_sp.png

advantage_icon03_sp.png

1164 ms

advantage_icon04.png

advantage_icon04.png

1251 ms

advantage_icon04_sp.png

advantage_icon04_sp.png

1244 ms

sub_icon03.png

sub_icon03.png

1157 ms

arrow4_r.png

arrow4_r.png

1109 ms

simulator_bg01.png

simulator_bg01.png

1109 ms

simulator_bg02.png

simulator_bg02.png

1098 ms

bg01.png

bg01.png

1135 ms

btn01.png

btn01.png

1069 ms

question_03_02.png

question_03_02.png

1089 ms

question_03_01.png

question_03_01.png

1025 ms

question_01_02_new.png

question_01_02_new.png

960 ms

question_01_03.png

question_01_03.png

945 ms

question_01_01.png

question_01_01.png

1063 ms

question_02_02.png

question_02_02.png

1061 ms

question_02_01.png

question_02_01.png

1022 ms

question_04_02_1.png

question_04_02_1.png

958 ms

question_04_02_1_sp.png

question_04_02_1_sp.png

943 ms

question_04_02.png

question_04_02.png

946 ms

question_04_01.png

question_04_01.png

1022 ms

foot_logo1.png

foot_logo1.png

943 ms

arrow6_r.png

arrow6_r.png

938 ms

foot_icon1.png

foot_icon1.png

941 ms

foot_logo2.png

foot_logo2.png

940 ms

foot_mail.png

foot_mail.png

910 ms

uammk7000000mowt.png

uammk7000000mowt.png

1722 ms

bx_loader.gif

bx_loader.gif

159 ms

arrow2_l.png

arrow2_l.png

157 ms

arrow2_r.png

arrow2_r.png

157 ms

Accessibility Review

geo-mobile.jp accessibility score

89

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

geo-mobile.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

geo-mobile.jp SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

geo-mobile.jp

Open Graph description is not detected on the main page of Geo Mobile. 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: