Tools & Wizards About Us
globus.jp screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

globus.jp

Holiday Packages, Tours & Experiences from Globus Tours

Page Load Speed

17 sec in total

First Response

1.9 sec

Resources Loaded

13.4 sec

Page Rendered

1.6 sec

globus.jp screenshot

About Website

Click here to check amazing Globus content. Otherwise, check out these important facts you probably never knew about globus.jp

Globus Tours provides first-class travel and more than 90 years of touring expertise and experience. There's no better way to experience your next holiday.

Visit globus.jp

Key Findings

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

Performance Metrics

globus.jp performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value24.6 s

0/100

25%

SI (Speed Index)

Value18.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.714

7/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

www.globus.jp

1917 ms

FormLoader.bundle.js

4793 ms

iframeResizer.min.js

67 ms

ws-tracking.js

34 ms

globus.css

2289 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 62% of them (34 requests) were addressed to the original Globus.jp, 9% (5 requests) were made to Use.typekit.net and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (4.8 sec) relates to the external source Cxppusa1formui01cdnsa01-endpoint.azureedge.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 544.7 kB (8%)

Content Size

6.8 MB

After Optimization

6.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 141.9 kB

  • Original 164.1 kB
  • After minification 144.0 kB
  • After compression 22.3 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 20.1 kB, which is 12% 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 141.9 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 99.4 kB

  • Original 4.7 MB
  • After minification 4.6 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. Globus images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 132.8 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 1.3 MB

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

-31%

Potential reduce by 170.6 kB

  • Original 547.8 kB
  • After minification 547.8 kB
  • After compression 377.1 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. Globus.jp needs all CSS files to be minified and compressed as it can save up to 170.6 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (26%)

Requests Now

43

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.globus.jp

www.globus.jp

1917 ms

FormLoader.bundle.js

FormLoader.bundle.js

4793 ms

iframeResizer.min.js

iframeResizer.min.js

67 ms

ws-tracking.js

ws-tracking.js

34 ms

globus.css

globus.css

2289 ms

VisitorIdentification.js

VisitorIdentification.js

1048 ms

uhk7arx.css

uhk7arx.css

67 ms

ai.2.min.js

ai.2.min.js

32 ms

elmosoftware.com.au

elmosoftware.com.au

269 ms

constants

constants

642 ms

contact-data-services.min.js

contact-data-services.min.js

919 ms

vendor.bundle.js

vendor.bundle.js

2863 ms

globus.js

globus.js

1776 ms

gtm.js

gtm.js

142 ms

globus-logo-red.svg

globus-logo-red.svg

621 ms

cosmos-logo.svg

cosmos-logo.svg

397 ms

avalon-blk-150x75.svg

avalon-blk-150x75.svg

292 ms

globus-usp-highlight-castle.jpg

globus-usp-highlight-castle.jpg

1112 ms

globus-usp-highlight-cooking.jpg

globus-usp-highlight-cooking.jpg

546 ms

globus-usp-highlight-tour-director.jpg

globus-usp-highlight-tour-director.jpg

545 ms

globus-usp-highlight-taormina.jpg

globus-usp-highlight-taormina.jpg

1165 ms

trees4travel-700x450.jpg

trees4travel-700x450.jpg

1087 ms

globus-country-header-ireland.jpg

globus-country-header-ireland.jpg

968 ms

globus-highlight-canada-quebec.jpg

globus-highlight-canada-quebec.jpg

818 ms

globus-highlight-greece-meteora.jpg

globus-highlight-greece-meteora.jpg

1775 ms

globus-logo-white.svg

globus-logo-white.svg

1065 ms

p.css

p.css

31 ms

220907_glo_header2.jpg

220907_glo_header2.jpg

1367 ms

201103_stonsaltpans_3000x2000px.jpg

201103_stonsaltpans_3000x2000px.jpg

1278 ms

undiscovered-enchanted-new-mexico-1700x550.jpg

undiscovered-enchanted-new-mexico-1700x550.jpg

1330 ms

lake_tahoe_3000x2000.jpg

lake_tahoe_3000x2000.jpg

1301 ms

galway_3000x2000.jpg

galway_3000x2000.jpg

1354 ms

pb-rugged-tasmania-tour-header-freycinet.jpg

pb-rugged-tasmania-tour-header-freycinet.jpg

1581 ms

header_peru_south_america_inca_3000x2000_2.jpg

header_peru_south_america_inca_3000x2000_2.jpg

1565 ms

globus-banner-generic-1412x200.jpg

globus-banner-generic-1412x200.jpg

1661 ms

globus-xp-highlight-solo-696x696.jpg

globus-xp-highlight-solo-696x696.jpg

3799 ms

globus-xp-highlight-independent-815x550.jpg

globus-xp-highlight-independent-815x550.jpg

1678 ms

globus-xp-highlight-escapes-1.jpg

globus-xp-highlight-escapes-1.jpg

1858 ms

Montserrat-Medium.ttf

Montserrat-Medium.ttf

1602 ms

d

d

101 ms

d

d

102 ms

d

d

122 ms

d

d

252 ms

Montserrat-Bold.ttf

Montserrat-Bold.ttf

1710 ms

Montserrat-SemiBold.ttf

Montserrat-SemiBold.ttf

1783 ms

Montserrat-Light.ttf

Montserrat-Light.ttf

1960 ms

js

js

100 ms

analytics.js

analytics.js

64 ms

matomo.js

matomo.js

1579 ms

cookieControl-8.x.min.js

cookieControl-8.x.min.js

69 ms

collect

collect

16 ms

v

v

362 ms

matomo.php

matomo.php

2592 ms

M1YAxc0U

M1YAxc0U

979 ms

track

track

211 ms

Accessibility Review

globus.jp accessibility score

64

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-*] attributes do not match their roles

High

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

globus.jp SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Globus.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Globus.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

globus.jp

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