Access livepocket.jp. LivePocket-Ticket-|電子チケット予約・購入・イベント検索

name

value

score

weighting

FCP (First Contentful Paint)

Value9.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value3,740 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.073

96/100

15%

TTI (Time to Interactive)

Value27.0 s

0/100

10%

livepocket.jp

336 ms

t.livepocket.jp

3243 ms

import.css

583 ms

add_class.css

902 ms

jquery-ui.css

717 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Livepocket.jp, 66% (81 requests) were made to T.livepocket.jp and 16% (20 requests) were made to Cdn.livepocket.jp. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source T.livepocket.jp.

Content Size

9.3 MB

After Optimization

6.4 MB

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

HTML Optimization

-84%

Potential reduce by 101.6 kB

Original 120.8 kB
After minification 78.6 kB
After compression 19.2 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 42.2 kB, which is 35% 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 101.6 kB or 84% of the original size.

Image Optimization

-24%

Potential reduce by 1.9 MB

Original 7.8 MB
After minification 5.9 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. Obviously, Live Pocket needs image optimization as it can save up to 1.9 MB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 548.0 kB

Original 936.0 kB
After minification 760.1 kB
After compression 388.0 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 548.0 kB or 59% of the original size.

CSS Optimization

-86%

Potential reduce by 411.5 kB

Original 479.6 kB
After minification 326.6 kB
After compression 68.2 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. Livepocket.jp needs all CSS files to be minified and compressed as it can save up to 411.5 kB or 86% of the original size.

Requests Now

110

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

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

livepocket.jp

Open Graph data is detected on the main page of Live Pocket. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

LivePocket-Ticket-|電子チケット予約・購入・イベント検索

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

livepocket.jp

t.livepocket.jp

import.css

add_class.css

jquery-ui.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

livepocket.jp

t.livepocket.jp

import.css

add_class.css

jquery-ui.css

jquery.fancybox-1.3.4.css

alertify.core.css

alertify.default.css

footer.css

global_top.css

goto_event_base.css

goto_event.css

banner.css

event_search.css

event_list_full_img2.css

jquery-jcflick.css

layout.css

jquery.glide.css

global_top.css

goto_event_base.css

slick.css

1

jquery.js

jquery-ui.min.js

jquery.ui.datepicker-ja.min.js

jquery.fancybox-1.3.4.js

jquery.vEllipsis.js

jquery.cj-object-scaler.min.js

alertify.min.js

jquery.skOuterClick.js

common.js

jquery.imgLiquid-min.js

cookie-common.js

common-count.js

jquery.tmpl.js

jquery.blockUI.js

sp-common.js

api.js

adsbygoogle.js

widget

P4kwS

exdate.js

util.js