14.2 sec in total
3.7 sec
9.9 sec
623 ms
Click here to check amazing Srx content for Singapore. Otherwise, check out these important facts you probably never knew about srx.com.sg
Singapore property & real estate portal to find quality house, HDB and Condo listings for sale & rent. Instant home valuation & recent transactions on Singapore's most trusted home pricing source.
Visit srx.com.sgWe analyzed Srx.com.sg page load time and found that the first response time was 3.7 sec and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
srx.com.sg performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value12.4 s
0/100
25%
Value13.4 s
2/100
10%
Value3,660 ms
1/100
30%
Value0.109
87/100
15%
Value23.4 s
1/100
10%
3659 ms
13 ms
77 ms
1104 ms
851 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 25% of them (28 requests) were addressed to the original Srx.com.sg, 30% (33 requests) were made to S3-ap-southeast-1.amazonaws.com and 13% (14 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Srx.com.sg.
Page size can be reduced by 539.8 kB (21%)
2.5 MB
2.0 MB
In fact, the total size of Srx.com.sg main page is 2.5 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. 55% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 354.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. 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 354.9 kB or 86% of the original size.
Potential reduce by 23.0 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. Srx images are well optimized though.
Potential reduce by 160.8 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 160.8 kB or 53% of the original size.
Potential reduce by 1.2 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. Srx.com.sg needs all CSS files to be minified and compressed as it can save up to 1.2 kB or 74% of the original size.
Number of requests can be reduced by 45 (48%)
93
48
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Srx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.srx.com.sg
3659 ms
gpt.js
13 ms
fbevents.js
77 ms
bootstrap.min.css
1104 ms
head.css
851 ms
main.css
855 ms
icon-srx-logo2.png
896 ms
logo.png
852 ms
icon_facebook_signin.png
855 ms
pubads_impl_81.js
10 ms
container.html
10 ms
29 ms
main-page-advert.png
2155 ms
main-page-v360.png
1132 ms
v360-icon.png
1407 ms
x-valuation.png
1418 ms
hotspot.png
1805 ms
0.jpg
78 ms
3240.jpg
1704 ms
13322.jpg
1768 ms
17462.jpg
1545 ms
3340.jpg
1985 ms
15952.jpg
1641 ms
15922.jpg
3047 ms
15312.jpg
2292 ms
15972.jpg
2314 ms
15962.jpg
2147 ms
15892.jpg
2291 ms
15802.jpg
2374 ms
15742.jpg
2412 ms
15712.jpg
2645 ms
15632.jpg
2649 ms
15622.jpg
2767 ms
button_download_srx_apps.png
2592 ms
button_subscribe_newsletter.png
2636 ms
cool-1.png
2825 ms
cool-2.png
2861 ms
cool-3.png
2867 ms
cool-4.png
2933 ms
banner-property-tracker-homepage-desktop.png
1606 ms
banner-property-tracker-homepage-mobile.png
1879 ms
button_play_video.png
1636 ms
css
77 ms
custombox.min.css
1928 ms
jquery.min.js
87 ms
bootstrap.min.js
44 ms
matchmedia.min.js
1646 ms
srx.printToPdf.min.js
2220 ms
enquire.min.js
1801 ms
legacy.min.js
1920 ms
custombox.min.js
2219 ms
typeahead.bundle.js
2476 ms
header.js
2602 ms
collapse.js
2755 ms
head.js
2756 ms
jquery.matchHeight-min.js
3071 ms
indexPage.js
3729 ms
icon_facebook.png
2771 ms
icon_twitter.png
2824 ms
icon_instagram.png
2862 ms
icon_youtube.png
2870 ms
background_4.jpg
2058 ms
image-gss-banner-2.png
1028 ms
icon-360-blue.png
1080 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
60 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
82 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
121 ms
glyphicons-halflings-regular.woff
1207 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
178 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
179 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
179 ms
all.js
112 ms
21 ms
xd_arbiter.php
131 ms
xd_arbiter.php
246 ms
ga.js
188 ms
analytics.js
186 ms
background_7.jpg
2003 ms
background_8.jpg
1786 ms
background_9.jpg
1586 ms
background_10.jpg
2219 ms
print.css
260 ms
xd_arbiter.php
77 ms
__utm.gif
19 ms
collect
15 ms
page.php
81 ms
page.php
82 ms
page.php
100 ms
collect
58 ms
q8sTdrz2ueE.css
163 ms
JvYiyYZV8Hs.css
201 ms
_rx8naC75Dy.js
311 ms
t-KLv3gqZy0.js
274 ms
uLtKx7ldlvR.js
350 ms
wFYNJ9lyaMJ.js
383 ms
Xs81m_2832G.js
400 ms
wyIfBc7KBcg.js
371 ms
12279157_546260225522448_2022197563337416023_n.jpg
254 ms
12278812_546250412190096_3607540550160962237_n.png
278 ms
12299321_1525152154473670_2910779945142719785_n.jpg
342 ms
11220475_1513945012261051_6386372332210092061_n.jpg
347 ms
12274566_978175785578828_5475784368507784525_n.jpg
354 ms
1450840_782217388508003_8717730199878328952_n.png
379 ms
wL6VQj7Ab77.png
84 ms
CSXXCvknpgK.png
84 ms
R9a_DtVRZgv.js
62 ms
cUDgRFxaoIk.js
62 ms
0JBr1QHp8Gi.js
61 ms
kDOzhTr2W91.js
61 ms
nr-885.min.js
41 ms
srx.com.sg accessibility score
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
[role]s do not have all required [aria-*] attributes
[aria-*] attributes do not have valid values
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
<object> elements do not have alternate text
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
srx.com.sg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
srx.com.sg SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Srx.com.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 Srx.com.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.
srx.com.sg
Open Graph description is not detected on the main page of Srx. 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: