Tools & Wizards About Us
touch.org.sg screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

touch.org.sg

TOUCH Community Services

Page Load Speed

14 sec in total

First Response

44 ms

Resources Loaded

13.8 sec

Page Rendered

209 ms

touch.org.sg screenshot

About Website

Click here to check amazing TOUCH Org content for Singapore. Otherwise, check out these important facts you probably never knew about touch.org.sg

We are a registered charity in Singapore, supporting individuals of all religions and races. Our services are designed to inspire hope and impact lives.

Visit touch.org.sg

Key Findings

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

Performance Metrics

touch.org.sg performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value33.7 s

0/100

25%

SI (Speed Index)

Value21.8 s

0/100

10%

TBT (Total Blocking Time)

Value2,830 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value32.9 s

0/100

10%

Network Requests Diagram

touch.org.sg

44 ms

touch.org.sg

5921 ms

gtm.js

97 ms

kendo.common.min.css

1781 ms

kendo.default.min.css

1039 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 62% of them (48 requests) were addressed to the original Touch.org.sg, 5% (4 requests) were made to Googletagmanager.com and 5% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Touch.org.sg.

Page Optimization Overview & Recommendations

Page size can be reduced by 624.8 kB (12%)

Content Size

5.1 MB

After Optimization

4.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Touch.org.sg main page is 5.1 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. 60% of websites need less resources to load. HTML takes 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-28%

Potential reduce by 517.1 kB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 1.3 MB

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 517.1 kB or 28% of the original size.

Image Optimization

-1%

Potential reduce by 13.9 kB

  • Original 1.3 MB
  • After minification 1.3 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. TOUCH Org images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 45.6 kB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 1.7 MB

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

-28%

Potential reduce by 48.3 kB

  • Original 173.2 kB
  • After minification 160.6 kB
  • After compression 124.9 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. Touch.org.sg needs all CSS files to be minified and compressed as it can save up to 48.3 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (68%)

Requests Now

71

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

touch.org.sg

touch.org.sg

44 ms

touch.org.sg

touch.org.sg

5921 ms

gtm.js

gtm.js

97 ms

kendo.common.min.css

kendo.common.min.css

1781 ms

kendo.default.min.css

kendo.default.min.css

1039 ms

jquery.min.js

jquery.min.js

1290 ms

js

js

182 ms

js

js

183 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

546 ms

layout_transformations.css

layout_transformations.css

1081 ms

bootstrap.min.css

bootstrap.min.css

1893 ms

slick.min.css

slick.min.css

1561 ms

owl.carousel.min.css

owl.carousel.min.css

1596 ms

themify-icons.css

themify-icons.css

2074 ms

style.css

style.css

3544 ms

flexslider.css

flexslider.css

2109 ms

fontawesome-all.min.css

fontawesome-all.min.css

2540 ms

WebForms.js

WebForms.js

47 ms

WebResource.axd

WebResource.axd

2041 ms

MicrosoftAjax.debug.js

MicrosoftAjax.debug.js

53 ms

MicrosoftAjaxWebForms.debug.js

MicrosoftAjaxWebForms.debug.js

49 ms

jquery-1.12.1.min.js

jquery-1.12.1.min.js

53 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

57 ms

js

js

61 ms

analytics.js

analytics.js

20 ms

collect

collect

14 ms

collect

collect

118 ms

collect

collect

108 ms

6649301.js

6649301.js

60 ms

fbevents.js

fbevents.js

26 ms

collect

collect

38 ms

bootstrap.min.js

bootstrap.min.js

772 ms

scripts.js

scripts.js

1524 ms

client.min.js

client.min.js

1040 ms

dropin.min.js

dropin.min.js

2425 ms

pay.js

pay.js

1230 ms

paypal-checkout.min.js

paypal-checkout.min.js

1607 ms

data-collector.min.js

data-collector.min.js

1560 ms

jquery.slicknav.min.js

jquery.slicknav.min.js

1560 ms

owl.carousel.min.js

owl.carousel.min.js

2260 ms

slick.min.js

slick.min.js

2520 ms

jquery.scrollUp.min.js

jquery.scrollUp.min.js

2033 ms

specialevent.js

specialevent.js

2083 ms

font-awesome.min.css

font-awesome.min.css

30 ms

kendo.custom.min.js

kendo.custom.min.js

4815 ms

kendo.pager.min.js

kendo.pager.min.js

2555 ms

kendo.all.min.js

kendo.all.min.js

6053 ms

kendo.aspnetmvc.min.js

kendo.aspnetmvc.min.js

3033 ms

kendo.culture.en-GB.min.js

kendo.culture.en-GB.min.js

2922 ms

Homepage.js

Homepage.js

3035 ms

css

css

37 ms

touch-site-logo.png

touch-site-logo.png

2387 ms

homeslide-1new.jpg

homeslide-1new.jpg

3993 ms

home-bannernew9.jpg

home-bannernew9.jpg

4245 ms

homeslide-3.jpg

homeslide-3.jpg

4111 ms

journey-banner-2023.png

journey-banner-2023.png

4411 ms

touch-icon1.png

touch-icon1.png

4518 ms

chan-siew-hock.jpg

chan-siew-hock.jpg

6579 ms

touch-footer-logo.png

touch-footer-logo.png

4638 ms

flUhRqu5zY00QEpyWJYWN59Yf_NeKBY.ttf

flUhRqu5zY00QEpyWJYWN59Yf_NeKBY.ttf

70 ms

flU8Rqu5zY00QEpyWJYWN5fzXeM.ttf

flU8Rqu5zY00QEpyWJYWN5fzXeM.ttf

89 ms

cse.js

cse.js

99 ms

sprites.png

sprites.png

4605 ms

btn-search-01.png

btn-search-01.png

4854 ms

homestories-bg.png

homestories-bg.png

4901 ms

fa-solid-900.woff

fa-solid-900.woff

6452 ms

fa-regular-400.woff

fa-regular-400.woff

6451 ms

cse_element__en.js

cse_element__en.js

20 ms

default+en.css

default+en.css

44 ms

default.css

default.css

46 ms

payframe

payframe

94 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

20 ms

cspreport

cspreport

107 ms

async-ads.js

async-ads.js

41 ms

branding.png

branding.png

38 ms

icon-profile.png

icon-profile.png

520 ms

highlight-bg-01.png

highlight-bg-01.png

535 ms

Accessibility Review

touch.org.sg accessibility score

81

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

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

Best Practices

touch.org.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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

touch.org.sg SEO score

92

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

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 Touch.org.sg 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 Touch.org.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

touch.org.sg

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