Tools & Wizards About Us
gomobile.jp screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

gomobile.jp

i3DESIGN アイスリーデザイン｜クラウドネイティブ、AI駆動開発、デザインシステム、モダナイゼーション

Page Load Speed

2.2 sec in total

First Response

12 ms

Resources Loaded

2 sec

Page Rendered

148 ms

gomobile.jp screenshot

About Website

Welcome to gomobile.jp homepage info - get ready to check Gomobile best content for Japan right away, or after learning these important things about gomobile.jp

クラウドネイティブ、AI駆動開発、デザインシステムに精通したDigital Innovatorです。UX/UIデザイン、モダンスタック技術、CI/CD、DevOps環境、AIエージェントをフル活用した開発スタイルで顧客のデジタルシフトを支援します。

Visit gomobile.jp

Key Findings

We analyzed Gomobile.jp page load time and found that the first response time was 12 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

gomobile.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value27.4 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value3,630 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value28.5 s

0/100

10%

Network Requests Diagram

gomobile.jp

12 ms

www.i3design.jp

17 ms

www.i3design.jp

40 ms

gtm.js

512 ms

v2.js

54 ms

Our browser made a total of 156 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gomobile.jp, 83% (129 requests) were made to I3design.jp and 6% (10 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source I3design.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (31%)

Content Size

4.5 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gomobile.jp main page is 4.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. Only a small number of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 1.2 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 315.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 1.2 MB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 233.9 kB

  • Original 2.6 MB
  • After minification 2.3 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. Gomobile images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.5 kB

  • Original 379.5 kB
  • After minification 379.5 kB
  • After compression 375.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 3.4 kB

  • Original 131.1 kB
  • After minification 131.1 kB
  • After compression 127.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. Gomobile.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 83 (63%)

Requests Now

131

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gomobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

gomobile.jp

gomobile.jp

12 ms

www.i3design.jp

www.i3design.jp

17 ms

www.i3design.jp

www.i3design.jp

40 ms

gtm.js

gtm.js

512 ms

v2.js

v2.js

54 ms

5ab110a7671585c7d8fa.css

5ab110a7671585c7d8fa.css

25 ms

1ee3e30babd067df3e9c.css

1ee3e30babd067df3e9c.css

37 ms

3b6b4ffbed9fc3d11ae6.css

3b6b4ffbed9fc3d11ae6.css

46 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

33 ms

webpack-d2ce57e3105ed6ccb87e.js

webpack-d2ce57e3105ed6ccb87e.js

38 ms

framework-106d25c2ed81dc45938c.js

framework-106d25c2ed81dc45938c.js

35 ms

main-e35e53e94c4363b60e66.js

main-e35e53e94c4363b60e66.js

42 ms

_app-d96d5baa4795a49a101f.js

_app-d96d5baa4795a49a101f.js

38 ms

6331-8ec2a956e007e0943fb2.js

6331-8ec2a956e007e0943fb2.js

49 ms

6485-afa843191e5e67d3e6db.js

6485-afa843191e5e67d3e6db.js

40 ms

index-0eeea14559b6b95ee6d8.js

index-0eeea14559b6b95ee6d8.js

44 ms

_buildManifest.js

_buildManifest.js

42 ms

_ssgManifest.js

_ssgManifest.js

507 ms

p.css

p.css

39 ms

p.css

p.css

35 ms

ns.html

ns.html

193 ms

a8140459580431a9db2b.css

a8140459580431a9db2b.css

33 ms

2185.c8e672736d80df3f35d3.js

2185.c8e672736d80df3f35d3.js

32 ms

_error-cd3a4dcc303cc09fa80f.js

_error-cd3a4dcc303cc09fa80f.js

29 ms

logo_i3design.png

logo_i3design.png

23 ms

direction_gray.svg

direction_gray.svg

24 ms

direction_white.svg

direction_white.svg

27 ms

icon_modern_application.svg

icon_modern_application.svg

155 ms

direction_block.svg

direction_block.svg

192 ms

icon_digital_poc.svg

icon_digital_poc.svg

29 ms

icon_digital_innovation%20support.svg

icon_digital_innovation%20support.svg

157 ms

icon_product_solution.svg

icon_product_solution.svg

28 ms

icon_flamingo.svg

icon_flamingo.svg

190 ms

icon_dressx.svg

icon_dressx.svg

158 ms

img_thum_kaiho.png

img_thum_kaiho.png

159 ms

img_thum_seyfert.png

img_thum_seyfert.png

192 ms

img_thum_kyosaimypage.png

img_thum_kyosaimypage.png

191 ms

img_thum_mms.png

img_thum_mms.png

203 ms

img_thum_meemo.png

img_thum_meemo.png

192 ms

img_thum_7net.png

img_thum_7net.png

205 ms

logo_docomo.png

logo_docomo.png

202 ms

logo_peachjohn.png

logo_peachjohn.png

260 ms

logo_seven.png

logo_seven.png

204 ms

logo_aeon.png

logo_aeon.png

204 ms

logo_nomura.png

logo_nomura.png

212 ms

logo_coop.png

logo_coop.png

211 ms

logo_kaneka.png

logo_kaneka.png

212 ms

logo_sompo.png

logo_sompo.png

211 ms

logo_ana.png

logo_ana.png

211 ms

logo_smbc.png

logo_smbc.png

250 ms

logo_disco.png

logo_disco.png

227 ms

logo_hitachi.png

logo_hitachi.png

230 ms

dxbootcamp01.jpg

dxbootcamp01.jpg

231 ms

direction_red.svg

direction_red.svg

224 ms

20240417_%E3%83%A1%E3%82%BF%E3%83%90%E3%83%BC%E3%82%B9%E3%82%BB%E3%83%9F%E3%83%8A%E3%83%BC-1.png

20240417_%E3%83%A1%E3%82%BF%E3%83%90%E3%83%BC%E3%82%B9%E3%82%BB%E3%83%9F%E3%83%8A%E3%83%BC-1.png

1447 ms

20240409.png

20240409.png

252 ms

d

d

205 ms

d

d

212 ms

d

d

225 ms

d

d

247 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75g.woff

324 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75g.woff

402 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75g.woff

401 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75g.woff

407 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk75g.woff

407 ms

d

d

246 ms

d

d

228 ms

d

d

226 ms

d

d

226 ms

d

d

228 ms

d

d

245 ms

20240319_i3design-1.png

20240319_i3design-1.png

242 ms

231 ms

235 ms

img_recruit_spB.jpg

img_recruit_spB.jpg

235 ms

img_contact02.png

img_contact02.png

233 ms

img_contact.png

img_contact.png

242 ms

logo_in-pocket.png

logo_in-pocket.png

235 ms

link_box_white.svg

link_box_white.svg

233 ms

%E3%83%8E%E3%83%BC%E3%82%B3%E3%83%BC%E3%83%89%E3%83%84%E3%83%BC%E3%83%AB%E8%A8%98%E4%BA%8B_%E3%82%B5%E3%83%A0%E3%83%8D%E3%82%A4%E3%83%AB.png

%E3%83%8E%E3%83%BC%E3%82%B3%E3%83%BC%E3%83%89%E3%83%84%E3%83%BC%E3%83%AB%E8%A8%98%E4%BA%8B_%E3%82%B5%E3%83%A0%E3%83%8D%E3%82%A4%E3%83%AB.png

1121 ms

%E3%83%8E%E3%83%BC%E3%82%B3%E3%83%BC%E3%83%89%E3%83%BB%E3%83%AD%E3%83%BC%E3%82%B3%E3%83%BC%E3%83%89-3%E3%81%A4%E3%81%AE%E8%90%BD%E3%81%A8%E3%81%97%E7%A9%B4.png

%E3%83%8E%E3%83%BC%E3%82%B3%E3%83%BC%E3%83%89%E3%83%BB%E3%83%AD%E3%83%BC%E3%82%B3%E3%83%BC%E3%83%89-3%E3%81%A4%E3%81%AE%E8%90%BD%E3%81%A8%E3%81%97%E7%A9%B4.png

279 ms

%E3%82%B5%E3%83%A0%E3%83%8D%E6%8E%A8%E3%81%97%E6%A1%88-1.png

%E3%82%B5%E3%83%A0%E3%83%8D%E6%8E%A8%E3%81%97%E6%A1%88-1.png

112 ms

%E3%83%97%E3%83%AD%E3%82%B8%E3%82%A7%E3%82%AF%E3%83%88%E3%83%87%E3%82%B6%E3%82%A4%E3%83%8A%E3%83%BC%E3%81%AE%E5%BD%B9%E5%89%B2%E3%82%92%E7%9F%A5%E3%82%8B.png

%E3%83%97%E3%83%AD%E3%82%B8%E3%82%A7%E3%82%AF%E3%83%88%E3%83%87%E3%82%B6%E3%82%A4%E3%83%8A%E3%83%BC%E3%81%AE%E5%BD%B9%E5%89%B2%E3%82%92%E7%9F%A5%E3%82%8B.png

1018 ms

img_intro_tech.png

img_intro_tech.png

129 ms

img_intro_note.png

img_intro_note.png

127 ms

index.json

index.json

133 ms

about.json

about.json

113 ms

brand.json

brand.json

135 ms

1.json

1.json

133 ms

1.json

1.json

133 ms

KFOlCnqEu92Fr1MmEU9vAA.woff

KFOlCnqEu92Fr1MmEU9vAA.woff

55 ms

link_box.svg

link_box.svg

199 ms

1ee3e30babd067df3e9c.css

1ee3e30babd067df3e9c.css

201 ms

3b6b4ffbed9fc3d11ae6.css

3b6b4ffbed9fc3d11ae6.css

125 ms

services-2494128ac944364d1b45.js

services-2494128ac944364d1b45.js

190 ms

e9cd7b107df9c215dc81.css

e9cd7b107df9c215dc81.css

191 ms

7238-3eec5c60a7370943c846.js

7238-3eec5c60a7370943c846.js

189 ms

5105-f49a7383ff789db518a2.js

5105-f49a7383ff789db518a2.js

192 ms

application-development-613ee803b1d9e3a9cdf0.js

application-development-613ee803b1d9e3a9cdf0.js

193 ms

1e84943eac8db114da14.css

1e84943eac8db114da14.css

202 ms

35b7341f4b79d93b24ac.css

35b7341f4b79d93b24ac.css

377 ms

devops-e8a5f97860973656998e.js

devops-e8a5f97860973656998e.js

200 ms

4cd8831e6c7e43a24bed.css

4cd8831e6c7e43a24bed.css

365 ms

cloud-0106acb53145ec2e2609.js

cloud-0106acb53145ec2e2609.js

366 ms

e3dbe57aa4bb5f52873e.css

e3dbe57aa4bb5f52873e.css

369 ms

design-system-9805ba78bb9e0a68ff82.js

design-system-9805ba78bb9e0a68ff82.js

363 ms

8b2479d3adca5cace6de.css

8b2479d3adca5cace6de.css

346 ms

73 ms

dc1c2e55d7e4d06a28bd.css

dc1c2e55d7e4d06a28bd.css

346 ms

uiuxdesign-94af5d479720530b8e48.js

uiuxdesign-94af5d479720530b8e48.js

343 ms

2418c871cbf7640bb546.css

2418c871cbf7640bb546.css

346 ms

15b5bf2d687f9ea53608.css

15b5bf2d687f9ea53608.css

344 ms

product-management-a745c27316fcdb055566.js

product-management-a745c27316fcdb055566.js

342 ms

83ec11fb1d1ca631fe79.css

83ec11fb1d1ca631fe79.css

346 ms

ai-0ed40c232b78027e1b5f.js

ai-0ed40c232b78027e1b5f.js

341 ms

b4fb941c8e22adee48ed.css

b4fb941c8e22adee48ed.css

342 ms

5716-99777b05805dad35d9eb.js

5716-99777b05805dad35d9eb.js

326 ms

xr-e59150e15d36711df7bc.js

xr-e59150e15d36711df7bc.js

324 ms

8ad5680d2e7a9f7783b2.css

8ad5680d2e7a9f7783b2.css

325 ms

106 ms

270cd077c7f35c4a6b01.css

270cd077c7f35c4a6b01.css

305 ms

1050-13529c77fcf7eb8083aa.js

1050-13529c77fcf7eb8083aa.js

303 ms

strategy-b859bc431dd2137238f9.js

strategy-b859bc431dd2137238f9.js

303 ms

276 ms

11ec169e5a57879dc3df.css

11ec169e5a57879dc3df.css

289 ms

dx-70d5557c647f30a71bcf.js

dx-70d5557c647f30a71bcf.js

288 ms

8d606666756a13a356e0.css

8d606666756a13a356e0.css

291 ms

hip-7d33c0aa4e9b94e682f0.js

hip-7d33c0aa4e9b94e682f0.js

285 ms

a262420e592156ca167f.css

a262420e592156ca167f.css

223 ms

flamingo-1855544094f0dfcec178.js

flamingo-1855544094f0dfcec178.js

224 ms

42dd9b4d97794bebf695.css

42dd9b4d97794bebf695.css

224 ms

dressx-dc407ec13858f1f09533.js

dressx-dc407ec13858f1f09533.js

219 ms

22a5caaf351755dd9126.css

22a5caaf351755dd9126.css

217 ms

download-1d42d32a3e17b2c957e3.js

download-1d42d32a3e17b2c957e3.js

217 ms

f7255d6ccceabad0d66b.css

f7255d6ccceabad0d66b.css

216 ms

contact-c26aba344bb60ce6feca.js

contact-c26aba344bb60ce6feca.js

209 ms

4ae76df37003ce011540.css

4ae76df37003ce011540.css

50 ms

3397-25fd1203702ae585f4fe.js

3397-25fd1203702ae585f4fe.js

48 ms

2437-c204aaad51b148cae80c.js

2437-c204aaad51b148cae80c.js

46 ms

cases-91e8a3a3c16ed5fc3682.js

cases-91e8a3a3c16ed5fc3682.js

46 ms

95118545905186016678.css

95118545905186016678.css

47 ms

about-792aa482365f2b4df6a5.js

about-792aa482365f2b4df6a5.js

43 ms

2831349f48f2dab5b522.css

2831349f48f2dab5b522.css

45 ms

brand-7bdb685cb70ff3c67d17.js

brand-7bdb685cb70ff3c67d17.js

46 ms

01320f9c6b683de0e36f.css

01320f9c6b683de0e36f.css

43 ms

%5Bid%5D-8a630a4dc9895769a210.js

%5Bid%5D-8a630a4dc9895769a210.js

43 ms

c2b0a7c57cde46e5d6ca.css

c2b0a7c57cde46e5d6ca.css

43 ms

recruit-427b8b3ed9f34bfa491f.js

recruit-427b8b3ed9f34bfa491f.js

43 ms

24dcfd57d149c82226cc.css

24dcfd57d149c82226cc.css

43 ms

privacy-ed4960fe3efd77613895.js

privacy-ed4960fe3efd77613895.js

42 ms

61165398243b909151cf.css

61165398243b909151cf.css

42 ms

%5Bid%5D-8be46c295e3d1a6313c5.js

%5Bid%5D-8be46c295e3d1a6313c5.js

41 ms

icon_x.svg

icon_x.svg

45 ms

icon_facebook.svg

icon_facebook.svg

40 ms

icon_wantedly.svg

icon_wantedly.svg

41 ms

icon_note.svg

icon_note.svg

54 ms

Accessibility Review

gomobile.jp accessibility score

85

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<html> element does not have a [lang] attribute

Best Practices

gomobile.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

gomobile.jp SEO score

92

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gomobile.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Gomobile.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

gomobile.jp

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