Tools & Wizards About Us
qct.io screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

qct.io

A leading datacenter hardware solution provider | QCT- Quanta Cloud Technology

Page Load Speed

7.1 sec in total

First Response

1.6 sec

Resources Loaded

5.2 sec

Page Rendered

246 ms

qct.io screenshot

About Website

Welcome to qct.io homepage info - get ready to check QCT best content for Taiwan right away, or after learning these important things about qct.io

Quanta Cloud Technology (QCT) is a global datacenter solution provider. We combine the efficiency of hyperscale hardware with infrastructure software from a diversity of industry leaders to solve next...

Visit qct.io

Key Findings

We analyzed Qct.io page load time and found that the first response time was 1.6 sec and then it took 5.4 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

qct.io performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

qct.io

1627 ms

sweetalert.css

9 ms

reset.css

7 ms

bootstrap.min.css

16 ms

jquery.mCustomScrollbar.min.css

14 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 90% of them (64 requests) were addressed to the original Qct.io, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Qct.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (53%)

Content Size

2.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qct.io main page is 2.4 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. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 50.4 kB

  • Original 61.1 kB
  • After minification 61.1 kB
  • After compression 10.8 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 50.4 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 12.0 kB

  • Original 800.9 kB
  • After minification 788.9 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. QCT images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 916.9 kB

  • Original 1.2 MB
  • After minification 1.0 MB
  • After compression 265.6 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 916.9 kB or 78% of the original size.

CSS Optimization

-83%

Potential reduce by 317.1 kB

  • Original 380.1 kB
  • After minification 372.7 kB
  • After compression 63.0 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. Qct.io needs all CSS files to be minified and compressed as it can save up to 317.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (59%)

Requests Now

63

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qct.io

qct.io

1627 ms

sweetalert.css

sweetalert.css

9 ms

reset.css

reset.css

7 ms

bootstrap.min.css

bootstrap.min.css

16 ms

jquery.mCustomScrollbar.min.css

jquery.mCustomScrollbar.min.css

14 ms

font-awesome.min.css

font-awesome.min.css

11 ms

animate.min.css

animate.min.css

21 ms

colorbox.css

colorbox.css

24 ms

video-js.css

video-js.css

25 ms

default.css

default.css

29 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

24 ms

jquery-ui.min.js

jquery-ui.min.js

44 ms

sweetalert.min.js

sweetalert.min.js

44 ms

jquery.mousewheel.js

jquery.mousewheel.js

26 ms

bootstrap.min.js

bootstrap.min.js

27 ms

jquery.mCustomScrollbar.min.js

jquery.mCustomScrollbar.min.js

42 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

42 ms

video.js

video.js

92 ms

yotube.js

yotube.js

64 ms

video_play.js

video_play.js

64 ms

init.js

init.js

65 ms

jquery.fullpage.min.css

jquery.fullpage.min.css

585 ms

iframe_api

iframe_api

40 ms

www-widgetapi.js

www-widgetapi.js

13 ms

swiper.min.css

swiper.min.css

6 ms

index.css

index.css

532 ms

jquery.fullpage.min.js

jquery.fullpage.min.js

534 ms

swiper.jquery.min.js

swiper.jquery.min.js

13 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

545 ms

jquery.loadie.min.js

jquery.loadie.min.js

554 ms

index.js

index.js

890 ms

gtm.js

gtm.js

265 ms

qct_logo.png

qct_logo.png

29 ms

qct_m_logo.svg

qct_m_logo.svg

26 ms

server_w_16092116167.svg

server_w_16092116167.svg

23 ms

storage_w_16092911763.svg

storage_w_16092911763.svg

34 ms

networking_w_16092911644.svg

networking_w_16092911644.svg

52 ms

rack_w_16092911633.svg

rack_w_16092911633.svg

29 ms

software_w_17031310463.svg

software_w_17031310463.svg

42 ms

Desktop_w_16092911444.svg

Desktop_w_16092911444.svg

36 ms

compute_w_16092911865.svg

compute_w_16092911865.svg

39 ms

storage_w_16092911937.svg

storage_w_16092911937.svg

44 ms

bigdate_w_16092911991.svg

bigdate_w_16092911991.svg

48 ms

QCT_2nd_GENERATION_SERVER_PLATFORMS_17071114253.jpg

QCT_2nd_GENERATION_SERVER_PLATFORMS_17071114253.jpg

549 ms

qct_home_icon.png

qct_home_icon.png

549 ms

qct_home_kv_next_icon.png

qct_home_kv_next_icon.png

567 ms

solution_center_16122110625.jpg

solution_center_16122110625.jpg

570 ms

Product-index-cover_16111017745.gif

Product-index-cover_16111017745.gif

557 ms

server_bk_16092910445.svg

server_bk_16092910445.svg

998 ms

storage_bk_16092911618.svg

storage_bk_16092911618.svg

1102 ms

networking_bk_16092911669.svg

networking_bk_16092911669.svg

1090 ms

rack_bk_16092911914.svg

rack_bk_16092911914.svg

1117 ms

Solution-index-cover_new_16123012128.gif

Solution-index-cover_new_16123012128.gif

1114 ms

qct_index_new_come.png

qct_index_new_come.png

1106 ms

QCT%20event-title-W%201190%20px%20%20H%20672%20px_17090611835.jpg

QCT%20event-title-W%201190%20px%20%20H%20672%20px_17090611835.jpg

2895 ms

facebook.png

facebook.png

1094 ms

twitter.png

twitter.png

1097 ms

linkedin.png

linkedin.png

1100 ms

google.png

google.png

1106 ms

flickr.png

flickr.png

1106 ms

youtube.png

youtube.png

1107 ms

qct_footer_img.png

qct_footer_img.png

1107 ms

OpenSans-Regular.ttf

OpenSans-Regular.ttf

1639 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1670 ms

MaterialIcons-Regular.woff

MaterialIcons-Regular.woff

2405 ms

OpenSans-Light.ttf

OpenSans-Light.ttf

1649 ms

OpenSans-Semibold.ttf

OpenSans-Semibold.ttf

1685 ms

analytics.js

analytics.js

5 ms

collect

collect

11 ms

collect

collect

49 ms

ga-audiences

ga-audiences

43 ms

Accessibility Review

qct.io accessibility score

64

Accessibility Issues

ARIA

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.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

qct.io best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

qct.io SEO score

85

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

qct.io

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