Tools & Wizards About Us
qs.sg screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

qs.sg

Experiential Design & Production | Digital Printing | Q’s Advertising

Page Load Speed

9 sec in total

First Response

616 ms

Resources Loaded

8.1 sec

Page Rendered

293 ms

qs.sg screenshot

About Website

Click here to check amazing Q S content. Otherwise, check out these important facts you probably never knew about qs.sg

Q's Advertising is a Singapore-based specialist in the creation of original and experiential design, production and digital printing. Contact us for more details!

Visit qs.sg

Key Findings

We analyzed Qs.sg page load time and found that the first response time was 616 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

qs.sg performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.6 s

0/100

25%

SI (Speed Index)

Value39.0 s

0/100

10%

TBT (Total Blocking Time)

Value730 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

Network Requests Diagram

qs.sg

616 ms

qs.sg

3235 ms

pattern-bg.png

462 ms

wp-emoji-release.min.js

592 ms

jquery.js

2188 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 60% of them (24 requests) were addressed to the original Qs.sg, 13% (5 requests) were made to Google.com and 13% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Qs.sg.

Page Optimization Overview & Recommendations

Page size can be reduced by 386.6 kB (44%)

Content Size

877.1 kB

After Optimization

490.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qs.sg main page is 877.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. 55% of websites need less resources to load. Javascripts take 417.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 337.1 kB

  • Original 397.7 kB
  • After minification 393.2 kB
  • After compression 60.5 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 337.1 kB or 85% of the original size.

Image Optimization

-18%

Potential reduce by 6.8 kB

  • Original 37.5 kB
  • After minification 30.7 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, Q S needs image optimization as it can save up to 6.8 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-10%

Potential reduce by 42.7 kB

  • Original 417.2 kB
  • After minification 416.2 kB
  • After compression 374.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 24.6 kB
  • After minification 24.6 kB
  • After compression 24.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. Qs.sg has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (61%)

Requests Now

31

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Q S. 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 as a result speed up the page load time.

Network Requests Diagram

qs.sg

qs.sg

616 ms

qs.sg

qs.sg

3235 ms

pattern-bg.png

pattern-bg.png

462 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

592 ms

jquery.js

jquery.js

2188 ms

jquery-migrate.min.js

jquery-migrate.min.js

770 ms

js

js

45 ms

plugin.min.js

plugin.min.js

1544 ms

autoptimize_single_566453b02257fd9b6bcfb327cae0d064.js

autoptimize_single_566453b02257fd9b6bcfb327cae0d064.js

896 ms

js

js

74 ms

autoptimize_single_f15811be6755dfe015332b46517a3d2b.js

autoptimize_single_f15811be6755dfe015332b46517a3d2b.js

927 ms

scripts.js

scripts.js

1026 ms

wpcf7-redirect-script.js

wpcf7-redirect-script.js

1201 ms

api.js

api.js

37 ms

api.js

api.js

60 ms

new-tab.min.js

new-tab.min.js

1239 ms

lazysizes.min.js

lazysizes.min.js

1283 ms

Gotham-Light.woff

Gotham-Light.woff

1928 ms

Jura-Regular.woff

Jura-Regular.woff

1276 ms

GothamBook.woff

GothamBook.woff

604 ms

Gotham-Medium.woff

Gotham-Medium.woff

1712 ms

recaptcha__en.js

recaptcha__en.js

40 ms

js

js

99 ms

shape1.png

shape1.png

274 ms

loader.gif

loader.gif

321 ms

Q-Logo.png

Q-Logo.png

508 ms

anchor

anchor

35 ms

styles__ltr.css

styles__ltr.css

4 ms

recaptcha__en.js

recaptcha__en.js

13 ms

email-icon.png

email-icon.png

491 ms

pattern-bg2.png

pattern-bg2.png

895 ms

fax-icon.png

fax-icon.png

649 ms

LdkrfvGznG7C1HMIvZeXpqeQHj2pK-25iJPmRAnKECo.js

LdkrfvGznG7C1HMIvZeXpqeQHj2pK-25iJPmRAnKECo.js

53 ms

webworker.js

webworker.js

51 ms

logo_48.png

logo_48.png

37 ms

tel-icon.png

tel-icon.png

736 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

58 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

60 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

60 ms

recaptcha__en.js

recaptcha__en.js

46 ms

Accessibility Review

qs.sg accessibility score

97

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

qs.sg 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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

qs.sg SEO score

84

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qs.sg can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Qs.sg 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

qs.sg

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