Tools & Wizards About Us
globaldata.jp screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

globaldata.jp

海外WiFiレンタルなら、イモトのWiFi｜24時間365日サポート

Page Load Speed

9.2 sec in total

First Response

551 ms

Resources Loaded

8.3 sec

Page Rendered

377 ms

globaldata.jp screenshot

About Website

Visit globaldata.jp now to see the best up-to-date Globaldata content for Japan and also check out these interesting facts you probably never knew about globaldata.jp

海外WiFiレンタル「イモトのWiFi」は海外旅行の必需品。海外でスマホやタブレットやPCと海外WiFiを一緒に使うとお得です。初めての海外WiFiレンタルでも24時間365日のサポートで安心。

Visit globaldata.jp

Key Findings

We analyzed Globaldata.jp page load time and found that the first response time was 551 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

globaldata.jp performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value23.1 s

0/100

25%

SI (Speed Index)

Value20.9 s

0/100

10%

TBT (Total Blocking Time)

Value6,370 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.308

38/100

15%

TTI (Time to Interactive)

Value48.5 s

0/100

10%

Network Requests Diagram

globaldata.jp

551 ms

www.globaldata.jp

1246 ms

font-awesome.min.css

531 ms

common.css

557 ms

layout.css

380 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 72% of them (90 requests) were addressed to the original Globaldata.jp, 6% (7 requests) were made to Facebook.com and 2% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Globaldata.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 319.3 kB (25%)

Content Size

1.3 MB

After Optimization

981.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Globaldata.jp main page is 1.3 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 913.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 84.0 kB

  • Original 102.6 kB
  • After minification 93.2 kB
  • After compression 18.6 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 84.0 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 23.4 kB

  • Original 913.0 kB
  • After minification 889.5 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. Globaldata images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 119.9 kB

  • Original 172.5 kB
  • After minification 154.2 kB
  • After compression 52.6 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 119.9 kB or 70% of the original size.

CSS Optimization

-82%

Potential reduce by 91.9 kB

  • Original 112.7 kB
  • After minification 92.9 kB
  • After compression 20.8 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. Globaldata.jp needs all CSS files to be minified and compressed as it can save up to 91.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (48%)

Requests Now

120

After Optimization

63

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

globaldata.jp

globaldata.jp

551 ms

www.globaldata.jp

www.globaldata.jp

1246 ms

font-awesome.min.css

font-awesome.min.css

531 ms

common.css

common.css

557 ms

layout.css

layout.css

380 ms

jquery-ui.css

jquery-ui.css

70 ms

css

css

74 ms

p_top_new.css

p_top_new.css

574 ms

slider-pro.min.css

slider-pro.min.css

393 ms

gmenu2.css

gmenu2.css

776 ms

jquery.min.js

jquery.min.js

31 ms

jquery-ui.js

jquery-ui.js

7 ms

jquery.ui.datepicker-ja.js

jquery.ui.datepicker-ja.js

371 ms

HolidayChk.js

HolidayChk.js

375 ms

jquery.sliderPro.min.js

jquery.sliderPro.min.js

942 ms

top.js

top.js

561 ms

def.js

def.js

397 ms

jquery.scrollButton.js

jquery.scrollButton.js

613 ms

jquery.tile.min.js

jquery.tile.min.js

715 ms

nexRt.js

nexRt.js

11 ms

conversion.js

conversion.js

18 ms

s_retargeting.js

s_retargeting.js

543 ms

conversion.js

conversion.js

919 ms

oct.js

oct.js

53 ms

fbds.js

fbds.js

78 ms

analytics.js

analytics.js

76 ms

logo_pgd.png

logo_pgd.png

485 ms

mypage_ico.png

mypage_ico.png

562 ms

head_contact.gif

head_contact.gif

693 ms

link_blank_icon.gif

link_blank_icon.gif

757 ms

gmenu.gif

gmenu.gif

850 ms

submenu_nav_bl.png

submenu_nav_bl.png

849 ms

entry_btn2.png

entry_btn2.png

1120 ms

n_info.png

n_info.png

1059 ms

n_bg.png

n_bg.png

1627 ms

n_simtitle.png

n_simtitle.png

1155 ms

n_slide_gkcp.png

n_slide_gkcp.png

1611 ms

n_slide_ltecp.png

n_slide_ltecp.png

1952 ms

n_slide_hm.png

n_slide_hm.png

2014 ms

n_slide03.png

n_slide03.png

1850 ms

n_slide04.png

n_slide04.png

1872 ms

n_slide_cm.png

n_slide_cm.png

2447 ms

n_thum_gkcp.png

n_thum_gkcp.png

1978 ms

n_thum_ltecp.png

n_thum_ltecp.png

2212 ms

n_thum_hm.png

n_thum_hm.png

2234 ms

n_thum03.png

n_thum03.png

2333 ms

n_thum04.png

n_thum04.png

2336 ms

n_thum_cm.png

n_thum_cm.png

2396 ms

bg_p.gif

bg_p.gif

2609 ms

n_ds01.png

n_ds01.png

2598 ms

n_merit01.png

n_merit01.png

2703 ms

n_merit02.png

n_merit02.png

2731 ms

n_merit03.png

n_merit03.png

2774 ms

n_s_title.png

n_s_title.png

2855 ms

n_ss_title.png

n_ss_title.png

2941 ms

collect

collect

35 ms

collect

collect

61 ms

37 ms

ga-audiences

ga-audiences

40 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

3428 ms

n_bg_tool01.png

n_bg_tool01.png

2936 ms

n_bg_tool02.png

n_bg_tool02.png

2924 ms

n_bn02.png

n_bn02.png

2851 ms

n_bn03.png

n_bn03.png

2864 ms

n_bn04.png

n_bn04.png

2877 ms

n_bn_jpw.png

n_bn_jpw.png

2975 ms

n_sm01.png

n_sm01.png

2921 ms

n_sm02.png

n_sm02.png

2917 ms

5 ms

fbevents.js

fbevents.js

18 ms

7 ms

rt

rt

296 ms

n_sm03.png

n_sm03.png

2895 ms

36 ms

blade_track_jp.js

blade_track_jp.js

372 ms

conversion.js

conversion.js

565 ms

4 ms

5 ms

14 ms

n_sm04.png

n_sm04.png

2952 ms

n_sm05.png

n_sm05.png

2991 ms

n_sm06.png

n_sm06.png

3000 ms

n_bn_mj.png

n_bn_mj.png

2871 ms

cookie_enabled_get.html

cookie_enabled_get.html

371 ms

n_bn_ft.png

n_bn_ft.png

2817 ms

n_m_title.png

n_m_title.png

2819 ms

beacon.gif

beacon.gif

177 ms

832 ms

adsct

adsct

93 ms

adsct

adsct

57 ms

ui-bg_inset-hard_100_fcfdfd_1x100.png

ui-bg_inset-hard_100_fcfdfd_1x100.png

10 ms

bl_track.cgi

bl_track.cgi

338 ms

n_arrow_r.png

n_arrow_r.png

2479 ms

n_flowimg01.png

n_flowimg01.png

2597 ms

n_flowimg02.png

n_flowimg02.png

2381 ms

n_flowimg03.png

n_flowimg03.png

2582 ms

n_flowimg04.png

n_flowimg04.png

2333 ms

n_flowimg05.png

n_flowimg05.png

2386 ms

c_visa.gif

c_visa.gif

2457 ms

c_mastar.gif

c_mastar.gif

2391 ms

c_amex.gif

c_amex.gif

2393 ms

c_jcb.gif

c_jcb.gif

2346 ms

c_diners.gif

c_diners.gif

2410 ms

n_flow.png

n_flow.png

2658 ms

icon_news.gif

icon_news.gif

2394 ms

imoto_wifi.png

imoto_wifi.png

2823 ms

banav01.jpg

banav01.jpg

2401 ms

banav02_sp.jpg

banav02_sp.jpg

2343 ms

banav03.jpg

banav03.jpg

2398 ms

banav04.jpg

banav04.jpg

2432 ms

media_bg.gif

media_bg.gif

2529 ms

n_story_img.png

n_story_img.png

2599 ms

n_story_ico.png

n_story_ico.png

2348 ms

foot_bg.gif

foot_bg.gif

2425 ms

foot_icon_home.png

foot_icon_home.png

2400 ms

foot_ul_icon.png

foot_ul_icon.png

2516 ms

foot_li_icon.png

foot_li_icon.png

2417 ms

foot_logo.gif

foot_logo.gif

2348 ms

csr.png

csr.png

2395 ms

foot_contact.gif

foot_contact.gif

2361 ms

foot_contact_bar.gif

foot_contact_bar.gif

2369 ms

openhand.cur

openhand.cur

2530 ms

vms.js

vms.js

82 ms

3 ms

4 ms

Accessibility Review

globaldata.jp accessibility score

79

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

globaldata.jp best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

globaldata.jp SEO score

75

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

globaldata.jp

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