Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 39

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

uukyoto.com

ゆうゆう京都観光タクシー 〜京都の個人タクシーのグループです〜

Page Load Speed

23.2 sec in total

First Response

551 ms

Resources Loaded

22.4 sec

Page Rendered

186 ms

uukyoto.com screenshot

About Website

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

ゆうゆう京都観光タクシー を始めて21年!!最大2時間超50%割引の認可を受けた観光タクシー:特定大型車・キャラバン8時間34,900円!! ・普通車8時間31,920円をご用意。京都観光するなら個人タクシーグループ『ゆうゆう京都観光タクシー』におまかせ!タクシー・ 舞妓・紅葉・桜・庭園・社寺・京都観光・観光案内・京都旅行・はゆうゆう京都観光タクシーで!!

Visit uukyoto.com

Key Findings

We analyzed Uukyoto.com page load time and found that the first response time was 551 ms and then it took 22.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

uukyoto.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value2,680 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

uukyoto.com

551 ms

uukyoto.com

879 ms

css.css

339 ms

AC_ActiveX.js

510 ms

AC_RunActiveContent.js

691 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 46% of them (35 requests) were addressed to the original Uukyoto.com, 16% (12 requests) were made to Youtube.com and 5% (4 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Wj.ax.xrea.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.3 kB (21%)

Content Size

926.0 kB

After Optimization

732.7 kB

In fact, the total size of Uukyoto.com main page is 926.0 kB. 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. Javascripts take 708.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 38.9 kB

  • Original 50.4 kB
  • After minification 44.2 kB
  • After compression 11.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 6.2 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 38.9 kB or 77% of the original size.

Image Optimization

-14%

Potential reduce by 6.1 kB

  • Original 43.9 kB
  • After minification 37.9 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. Obviously, Uukyoto needs image optimization as it can save up to 6.1 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 144.2 kB

  • Original 708.1 kB
  • After minification 708.0 kB
  • After compression 563.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 144.2 kB or 20% of the original size.

CSS Optimization

-3%

Potential reduce by 4.1 kB

  • Original 123.6 kB
  • After minification 122.4 kB
  • After compression 119.5 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. Uukyoto.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (35%)

Requests Now

63

After Optimization

41

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

Accessibility Review

uukyoto.com accessibility score

39

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.

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

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

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

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

Best Practices

uukyoto.com best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

uukyoto.com SEO score

58

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uukyoto.com 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 Uukyoto.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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