4.4 sec in total
618 ms
3 sec
785 ms
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
i3DESIGNは、UI/UXデザインとテクノロジーに強みを持つ新世代のDX支援会社です。デザイン思考のアプローチでクライアントの新規事業の創出からグロースまでDXを支援します。
Visit gomobile.jpWe analyzed Gomobile.jp page load time and found that the first response time was 618 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
gomobile.jp performance score
name
value
score
weighting
Value10.7 s
0/100
10%
Value11.1 s
0/100
25%
Value12.1 s
3/100
10%
Value940 ms
30/100
30%
Value0.004
100/100
15%
Value15.6 s
6/100
10%
618 ms
258 ms
375 ms
547 ms
362 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 75% of them (33 requests) were addressed to the original Gomobile.jp, 9% (4 requests) were made to I3design.jp and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source I3design.jp.
Page size can be reduced by 378.7 kB (23%)
1.6 MB
1.2 MB
In fact, the total size of Gomobile.jp main page is 1.6 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. 40% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 16.5 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 3.1 kB, which is 13% 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 16.5 kB or 70% of the original size.
Potential reduce by 943 B
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.
Potential reduce by 267.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 267.9 kB or 65% of the original size.
Potential reduce by 93.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. Gomobile.jp needs all CSS files to be minified and compressed as it can save up to 93.3 kB or 86% of the original size.
Number of requests can be reduced by 9 (45%)
20
11
The browser has sent 20 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 10 to 1 for JavaScripts and as a result speed up the page load time.
gomobile.jp
618 ms
style.css
258 ms
swiper.min.css
375 ms
jquery-1.11.3.min.js
547 ms
main.js
362 ms
jquery.sameheight.js
338 ms
swiper.min.js
515 ms
jcf.css
459 ms
jcf.js
571 ms
jcf.select.js
579 ms
js
53 ms
mapstyle.js
613 ms
1762742417.js
479 ms
event
81 ms
analytics.js
70 ms
logo.png
238 ms
main_logo.jpg
1658 ms
1-1.jpg
1642 ms
6.jpg
1506 ms
social-1035053_12802.jpg
1211 ms
ico-nav-open.png
191 ms
img-gtop01.jpg
689 ms
ico-what-we-do03.png
241 ms
ico-what-we-do02.png
198 ms
ico-what-we-do01.png
234 ms
arrow03.png
374 ms
ico-solutions.png
547 ms
img-swiper01.jpg
679 ms
img-swiper02.png
883 ms
img-swiper03.png
929 ms
img-swiper04.png
1024 ms
arrow-r01.png
740 ms
arrow-l01.png
866 ms
part-logo-co01.png
894 ms
part-logo-co02.png
1193 ms
part-logo-co03.png
1059 ms
part-logo-co04.png
1081 ms
part-logo-co05.png
1181 ms
part-logo-co06.png
1158 ms
arrow02.png
1213 ms
logo-footer.png
1252 ms
collect
2 ms
collect
67 ms
ga-audiences
70 ms
gomobile.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
Buttons do not have an accessible name
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 [lang] attribute
gomobile.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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
gomobile.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
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.
gomobile.jp
Open Graph data is detected on the main page of Gomobile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: