7.2 sec in total
535 ms
6.2 sec
418 ms
Visit src.org.sg now to see the best up-to-date Src Org content and also check out these interesting facts you probably never knew about src.org.sg
The Singapore Recreation Club (SRC) was founded on 23 June 1883 by a group of thirty Eurasian men and was officially established on 1 July 1883. At that time, the Club was housed in a building on Wate...
Visit src.org.sgWe analyzed Src.org.sg page load time and found that the first response time was 535 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
src.org.sg performance score
name
value
score
weighting
Value11.1 s
0/100
10%
Value34.5 s
0/100
25%
Value18.3 s
0/100
10%
Value330 ms
75/100
30%
Value0.217
57/100
15%
Value17.3 s
4/100
10%
535 ms
1176 ms
229 ms
458 ms
684 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 97% of them (67 requests) were addressed to the original Src.org.sg, 1% (1 request) were made to Googletagmanager.com and 1% (1 request) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Src.org.sg.
Page size can be reduced by 218.2 kB (4%)
5.0 MB
4.8 MB
In fact, the total size of Src.org.sg main page is 5.0 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. 45% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 69.0 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 22.9 kB, which is 27% 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 69.0 kB or 82% of the original size.
Potential reduce by 14.4 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. Src Org images are well optimized though.
Potential reduce by 111.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 111.0 kB or 21% of the original size.
Potential reduce by 23.7 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. Src.org.sg needs all CSS files to be minified and compressed as it can save up to 23.7 kB or 37% of the original size.
Number of requests can be reduced by 31 (49%)
63
32
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Src 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 21 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
src.org.sg
535 ms
src.org.sg
1176 ms
sweetalert.css
229 ms
font-awesome.min.css
458 ms
component.css
684 ms
icons.css
910 ms
normalize.css
924 ms
modernizr.custom.js
935 ms
jquery.min.js
1402 ms
jquery-3.4.1.js
1647 ms
jquery-3.4.1.min.js
1434 ms
jquery-ui.min.js
1380 ms
sweetalert-dev.js
1154 ms
MasterPage.css
1167 ms
Master.css
1383 ms
style.css
1638 ms
js
59 ms
owl.carousel.css
1608 ms
owl.carousel.min.js
1635 ms
owl.carousel.js
1721 ms
waterfullcomponent.css
1834 ms
modernizr.custom.js
1838 ms
jquery.fancybox.css
1865 ms
jquery.fancybox.js
1873 ms
jquery.fancybox-media.js
1876 ms
smallchange.css
1908 ms
WebResource.axd
2061 ms
ScriptResource.axd
2298 ms
ScriptResource.axd
2096 ms
classie.js
2102 ms
mlpushmenu.js
2107 ms
js
70 ms
masonry.pkgd.min.js
2143 ms
imagesloaded.js
2285 ms
AnimOnScroll.js
2380 ms
icon_fb.png
475 ms
icon_navilogin_mb.png
474 ms
logo.jpg
475 ms
footer_devider.png
606 ms
icon_in.png
658 ms
icon_navilogin.png
659 ms
icons_arrow_down.png
660 ms
355.jpg
1853 ms
356.jpg
1877 ms
357.jpg
1506 ms
354.jpg
1545 ms
353.jpg
1812 ms
332.jpg
1587 ms
263.jpg
1741 ms
262.jpg
1782 ms
261.jpg
1827 ms
260.jpg
1976 ms
258.jpg
2017 ms
home_location.jpg
2048 ms
icon_contactus.png
1646 ms
Jost-SemiBold.woff
1611 ms
OpenSans-Regular.ttf
1657 ms
TrajanPro-Regular.woff
1731 ms
TrajanPro-Bold.woff
1773 ms
linecons.dev.svg
1812 ms
home_annoucementbg.jpg
1788 ms
home_eventsbg.jpg
1840 ms
icon_homecalendar.png
1855 ms
dots-active.jpg
1842 ms
dots.jpg
1886 ms
home_calendar_arrowl.png
1861 ms
home_calendar_arrowr.png
1862 ms
home_calendarthbg.jpg
1928 ms
blackdot_hl.png
1946 ms
src.org.sg accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
src.org.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
src.org.sg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Src.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 Src.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.
src.org.sg
Open Graph description is not detected on the main page of Src 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: