Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

tw.pikolive.com

【PikoLive 皮克直播】免費第四台!直播、遊戲、新聞、實況、線上看、APP

Page Load Speed

8.2 sec in total

First Response

2.1 sec

Resources Loaded

5.6 sec

Page Rendered

500 ms

tw.pikolive.com screenshot

About Website

Click here to check amazing Tw Piko Live content for Taiwan. Otherwise, check out these important facts you probably never knew about tw.pikolive.com

實況、直播、網站、籃球、棒球、電影、動漫、動畫、卡通、LOL、DOTA、台灣、Taiwan、Twitch、YouTube、UStream、Vaughnlive、NBA、MLB、金曲獎、金馬獎、金鐘獎、奧斯卡

Visit tw.pikolive.com

Key Findings

We analyzed Tw.pikolive.com page load time and found that the first response time was 2.1 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

tw.pikolive.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.4 s

48/100

10%

Network Requests Diagram

tw.pikolive.com

2085 ms

jquery.min.js

36 ms

jquery-ui.css

12 ms

jquery-ui.js

12 ms

cssreset.css

161 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 27% of them (26 requests) were addressed to the original Tw.pikolive.com, 19% (18 requests) were made to Static-cdn.jtvnw.net and 11% (10 requests) were made to Snapshots-cdn.streamup.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Chrome.pikolive.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 227.6 kB (19%)

Content Size

1.2 MB

After Optimization

984.9 kB

In fact, the total size of Tw.pikolive.com main page is 1.2 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. 65% of websites need less resources to load. Images take 957.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 49.7 kB

  • Original 60.9 kB
  • After minification 50.5 kB
  • After compression 11.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 10.4 kB, which is 17% 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 49.7 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 83.6 kB

  • Original 957.8 kB
  • After minification 874.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. Tw Piko Live images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 74.1 kB

  • Original 160.7 kB
  • After minification 158.4 kB
  • After compression 86.7 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 74.1 kB or 46% of the original size.

CSS Optimization

-61%

Potential reduce by 20.2 kB

  • Original 33.1 kB
  • After minification 30.7 kB
  • After compression 12.9 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. Tw.pikolive.com needs all CSS files to be minified and compressed as it can save up to 20.2 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (31%)

Requests Now

89

After Optimization

61

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

Accessibility Review

tw.pikolive.com accessibility score

62

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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

Best Practices

tw.pikolive.com 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

Page has valid source maps

SEO Factors

tw.pikolive.com SEO score

82

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tw.pikolive.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Tw.pikolive.com 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

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