Access quickly.com.tw. 快克利雲端解決方案專家

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value19.6 s

0/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value11.7 s

18/100

10%

quickly.com.tw

4383 ms

style3c.css

416 ms

swfobject_modified.js

616 ms

header_02.jpg

812 ms

call.gif

417 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 68% of them (38 requests) were addressed to the original Quickly.com.tw, 18% (10 requests) were made to Static.xx.fbcdn.net and 5% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Quickly.com.tw.

Content Size

373.1 kB

After Optimization

177.0 kB

In fact, the total size of Quickly.com.tw main page is 373.1 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. 40% of websites need less resources to load. Images take 175.8 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 154.2 kB

Original 170.6 kB
After minification 113.7 kB
After compression 16.4 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 56.9 kB, which is 33% 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 154.2 kB or 90% of the original size.

Image Optimization

-11%

Potential reduce by 20.0 kB

Original 175.8 kB
After minification 155.8 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, Quickly needs image optimization as it can save up to 20.0 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

-81%

Potential reduce by 17.7 kB

Original 21.7 kB
After minification 13.2 kB
After compression 4.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 17.7 kB or 81% of the original size.

CSS Optimization

-85%

Potential reduce by 4.2 kB

Original 4.9 kB
After minification 4.1 kB
After compression 737 B

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. Quickly.com.tw needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 85% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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

High

Links do not have a discernible name

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 interpretation of your content by users in different locales.

High

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

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

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Page has valid source maps

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

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

Language and Encoding

Language Detected

ZH
Language Claimed

N/A
Encoding

BIG5

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Quickly.com.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 Quickly.com.tw main page’s claimed encoding is big5. 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

quickly.com.tw

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

快克利雲端解決方案專家 - 軟體 / 3C / 耗材

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

quickly.com.tw

style3c.css

swfobject_modified.js

header_02.jpg

call.gif

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

quickly.com.tw

style3c.css

swfobject_modified.js

header_02.jpg

call.gif

ad21.gif

ad5.gif

office365_160x600.jpg

facebookfans.jpg

ad7.gif

ad17.gif

ad2.gif

ad3.gif

ad15.jpg

header_03.jpg

header_01.jpg

780prowhite.jpg

780pro.jpg

cata4.gif

icon2.gif

cloud.jpg

cata1.gif

bu1.gif

linebk.gif

smallad1-1.gif

smallad3-1.gif

smallad2-1.gif

smallad4-1.gif

get_flash_player.gif

facebookbg3.gif

ad.jpg

cata5.gif

bu20x20.gif

sdk.js

office365.jpg

cata2.gif

cata3.gif

ms.gif

bu3.gif

msbig.gif

xd_arbiter.php

xd_arbiter.php

page.php