Access playmusic.tw. PlayMusic音樂社群網站

playmusic.tw screenshot

17

Performance

Renders faster than
32% of other websites
76

Accessibility

Visual factors better than
that of 42% of websites
50

Best Practices

More advanced features
available than in
19% of websites
54

SEO

Google-friendlier than
19% of websites

First Response

354 ms

Resources Loaded

5.9 sec

Page Rendered

208 ms

playmusic.tw screenshot

About Website

Click here to check amazing Play Music content for Taiwan. Otherwise, check out these important facts you probably never knew about playmusic.tw

PlayMusic音樂網、Play Music、Play Music 音樂網、音樂網、音樂、投票、音樂榜單、P-Music、樂評、新聞

Visit playmusic.tw

Key Findings

We analyzed Playmusic.tw page load time and found that the first response time was 354 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value10.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.74

6/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

playmusic.tw

354 ms

playmusic.tw

854 ms

jquery-1.8.3.min.js

498 ms

jquery-ui-1.9.2.js

1245 ms

global.js

474 ms

Our browser made a total of 159 requests to load all elements on the main page. We found that 84% of them (133 requests) were addressed to the original Playmusic.tw, 11% (18 requests) were made to Img.youtube.com and 1% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Playmusic.tw.

Content Size

2.8 MB

After Optimization

1.8 MB

In fact, the total size of Playmusic.tw main page is 2.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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 130.6 kB

Original 154.7 kB
After minification 126.3 kB
After compression 24.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 28.5 kB, which is 18% 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 130.6 kB or 84% of the original size.

Image Optimization

-11%

Potential reduce by 185.8 kB

Original 1.7 MB
After minification 1.5 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, Play Music needs image optimization as it can save up to 185.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-77%

Potential reduce by 633.0 kB

Original 818.6 kB
After minification 604.0 kB
After compression 185.5 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 633.0 kB or 77% of the original size.

CSS Optimization

-82%

Potential reduce by 114.0 kB

Original 139.7 kB
After minification 121.7 kB
After compression 25.6 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. Playmusic.tw needs all CSS files to be minified and compressed as it can save up to 114.0 kB or 82% of the original size.

Requests Now

156

After Optimization

124

The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Play Music. 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 12 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 keyboard navigation in your application.

High

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

High

Heading elements are not in a sequentially-descending order

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.

High

ARIA IDs are not unique

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

High

<object> elements do not have alternate text

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

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

High

Document uses plugins

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 Playmusic.tw 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 Playmusic.tw 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

playmusic.tw

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