Tools & Wizards About Us
upon.co.jp screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

upon.co.jp

バスツアー（日帰り・宿泊）＆格安夜行バス｜アップオン

Page Load Speed

3.8 sec in total

First Response

364 ms

Resources Loaded

3.3 sec

Page Rendered

134 ms

upon.co.jp screenshot

About Website

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

アップオンは快適・格安な旅を提供します！格安高速バス・夜行バスを始め、東京ディズニーリゾート、ユニバーサル・スタジオ・ジャパン、富士急ハイランド、ナガシマスパーランドなどテーマパーク＆アミューズメントパークへの格安ツアー満載♪

Visit upon.co.jp

Key Findings

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

Performance Metrics

upon.co.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value18.4 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value1.803

0/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

upon.co.jp

364 ms

www.upon.co.jp

751 ms

bootstrap.min.css

538 ms

basic.css

501 ms

style.css

502 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 88% of them (45 requests) were addressed to the original Upon.co.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to S.yjtag.jp. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Upon.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 316.9 kB (23%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Upon.co.jp main page is 1.4 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. 30% of websites need less resources to load. Images take 999.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 29.4 kB

  • Original 36.4 kB
  • After minification 27.8 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 8.6 kB, which is 24% 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 29.4 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 48.9 kB

  • Original 999.1 kB
  • After minification 950.2 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. Upon images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 135.9 kB

  • Original 206.7 kB
  • After minification 205.3 kB
  • After compression 70.8 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 135.9 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 102.7 kB

  • Original 125.4 kB
  • After minification 119.9 kB
  • After compression 22.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. Upon.co.jp needs all CSS files to be minified and compressed as it can save up to 102.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (39%)

Requests Now

49

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Upon. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

upon.co.jp

upon.co.jp

364 ms

www.upon.co.jp

www.upon.co.jp

751 ms

bootstrap.min.css

bootstrap.min.css

538 ms

basic.css

basic.css

501 ms

style.css

style.css

502 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

934 ms

bootstrap.min.js

bootstrap.min.js

713 ms

jquery.slides.min.js

jquery.slides.min.js

635 ms

slidersetup.js

slidersetup.js

666 ms

adcd.js

adcd.js

666 ms

colorbox.css

colorbox.css

714 ms

jquery.colorbox-orignal.js

jquery.colorbox-orignal.js

806 ms

scrl.js

scrl.js

831 ms

analytics.js

analytics.js

96 ms

tag.js

tag.js

113 ms

upons.jpg

upons.jpg

280 ms

ribon.png

ribon.png

689 ms

disney.jpg

disney.jpg

341 ms

disneytitle.png

disneytitle.png

424 ms

disneytitle2.png

disneytitle2.png

443 ms

img645.jpg

img645.jpg

443 ms

ribon.png

ribon.png

878 ms

img02.jpg

img02.jpg

735 ms

title.png

title.png

762 ms

camera.png

camera.png

609 ms

img01.jpg

img01.jpg

777 ms

banzai.jpg

banzai.jpg

1103 ms

play_arrow.png

play_arrow.png

866 ms

cube_tdr-min.jpg

cube_tdr-min.jpg

913 ms

cube_usj-min.jpg

cube_usj-min.jpg

953 ms

cube_fujiq-min.jpg

cube_fujiq-min.jpg

945 ms

cube_nagaspa-min.jpg

cube_nagaspa-min.jpg

1048 ms

cube_fuji.jpg

cube_fuji.jpg

1058 ms

ic_info_outline_grey600_36dp.png

ic_info_outline_grey600_36dp.png

1092 ms

ic_call_grey600_36dp.png

ic_call_grey600_36dp.png

1110 ms

ic_account_box_grey600_36dp.png

ic_account_box_grey600_36dp.png

1141 ms

ic_account_child_grey600_36dp.png

ic_account_child_grey600_36dp.png

1224 ms

ic_favorite_grey600_36dp.png

ic_favorite_grey600_36dp.png

1238 ms

ic_filter_vintage_grey600_24dp.png

ic_filter_vintage_grey600_24dp.png

1268 ms

cards.png

cards.png

1266 ms

cvss.png

cvss.png

1603 ms

bk1.png

bk1.png

1328 ms

bk2.png

bk2.png

1326 ms

pmark.png

pmark.png

1342 ms

collect

collect

13 ms

jata.png

jata.png

1325 ms

fairtrade.png

fairtrade.png

1350 ms

collect

collect

30 ms

js

js

63 ms

ga-audiences

ga-audiences

28 ms

logo.png

logo.png

1365 ms

Accessibility Review

upon.co.jp accessibility score

75

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

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

upon.co.jp best practices score

50

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

High

Browser errors were logged to the console

SEO Factors

upon.co.jp SEO score

91

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 Upon.co.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 Upon.co.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

upon.co.jp

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