Access xuite.net. 結束營運公告

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.0 s

0/100

25%

SI (Speed Index)

Value24.6 s

0/100

10%

TBT (Total Blocking Time)

Value3,770 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value1.001

2/100

15%

TTI (Time to Interactive)

Value35.0 s

0/100

10%

xuite.net

1161 ms

style.css

839 ms

cookie,cycle,jcarousel

1889 ms

common.css

629 ms

1114345747_m.jpg

2672 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Xuite.net, 34% (40 requests) were made to 1.share.photo.xuite.net and 9% (11 requests) were made to Img.xuite.net. The less responsive or slowest element that took the longest time to load (5.4 sec) relates to the external source 1.share.photo.xuite.net.

Content Size

8.8 MB

After Optimization

6.9 MB

In fact, the total size of Xuite.net main page is 8.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 6.3 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 208.4 kB

Original 235.3 kB
After minification 159.9 kB
After compression 26.9 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 75.4 kB, which is 32% 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 208.4 kB or 89% of the original size.

Image Optimization

-2%

Potential reduce by 128.3 kB

Original 6.3 MB
After minification 6.2 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. Xuite images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 1.1 MB

Original 1.6 MB
After minification 1.6 MB
After compression 568.4 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 1.1 MB or 65% of the original size.

CSS Optimization

-85%

Potential reduce by 569.9 kB

Original 674.2 kB
After minification 523.8 kB
After compression 104.4 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. Xuite.net needs all CSS files to be minified and compressed as it can save up to 569.9 kB or 85% 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 Xuite. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Issues

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Requests the notification permission on page load

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

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

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

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

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xuite.net 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 Xuite.net 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

xuite.net

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

Report Summary

Performance

Accessibility

Best Practices

SEO

結束營運公告 - 隨意窩

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

xuite.net

style.css

cookie,cycle,jcarousel

common.css

1114345747_m.jpg

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

xuite.net

style.css

cookie,cycle,jcarousel

common.css

1114345747_m.jpg

1116543269_x.jpg

index

1114347224_m.jpg

1114349670_m.jpg

1114349274_m.jpg

1114348108_m.jpg

1114345754_m.jpg

1114349476_m.jpg

1114333309_m.jpg

1114332542_m.jpg

1114333029_m.jpg

1114334120_m.jpg

1114333712_m.jpg

1114333418_m.jpg

1114332563_m.jpg

1116368084_m.jpg

1116368083_m.jpg

1116367585_m.jpg

1116365305_m.jpg

1116367683_m.jpg

1116365806_m.jpg

1116368478_m.jpg

1116215615_m.jpg

1116216211_m.jpg

1116213523_m.jpg

1116215528_m.jpg

1116215830_m.jpg

1116214944_m.jpg

1116213943_m.jpg

1114297077_m.jpg

1114298077_m.jpg

1114294341_m.jpg

1114298577_m.jpg

1114297699_m.jpg

1114299194_m.jpg

1114297493_m.jpg

1116399270_x.jpg

spinner_100x100.gif