7.9 sec in total
834 ms
6.7 sec
316 ms
Visit whatshappening.sg now to see the best up-to-date Whatshappening content for Singapore and also check out these interesting facts you probably never knew about whatshappening.sg
What's happening in Singapore, get the latest updates on events in Singapore.
Visit whatshappening.sgWe analyzed Whatshappening.sg page load time and found that the first response time was 834 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
whatshappening.sg performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value20.0 s
0/100
25%
Value18.3 s
0/100
10%
Value240 ms
85/100
30%
Value0.703
7/100
15%
Value19.2 s
2/100
10%
834 ms
1606 ms
525 ms
786 ms
527 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 40% of them (34 requests) were addressed to the original Whatshappening.sg, 8% (7 requests) were made to Pagead2.googlesyndication.com and 7% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Whatshappening.sg.
Page size can be reduced by 408.8 kB (37%)
1.1 MB
682.8 kB
In fact, the total size of Whatshappening.sg main page is 1.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. 55% of websites need less resources to load. Images take 599.9 kB which makes up the majority of the site volume.
Potential reduce by 64.7 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 64.7 kB or 85% of the original size.
Potential reduce by 50.8 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. Whatshappening images are well optimized though.
Potential reduce by 237.5 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 237.5 kB or 68% of the original size.
Potential reduce by 55.8 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. Whatshappening.sg needs all CSS files to be minified and compressed as it can save up to 55.8 kB or 82% of the original size.
Number of requests can be reduced by 40 (49%)
81
41
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whatshappening. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
whatshappening.sg
834 ms
1606 ms
core.css
525 ms
style.css
786 ms
style2.css
527 ms
helios.css
532 ms
AC_RunActiveContent.js
531 ms
buttons.js
8 ms
show_ads.js
5 ms
SNXX0006
94 ms
text_L.jpg
15 ms
btn_home_off.jpg
625 ms
btn_submitevent_off.jpg
602 ms
btn_searchevent_off.jpg
624 ms
btn_newsletter_off.jpg
625 ms
magic_glass.jpg
622 ms
search_go.jpg
623 ms
event_tag.png
1052 ms
calendar_header.jpg
1385 ms
FacebookButtonRevised-164-50.jpg
1648 ms
header-weather.gif
1133 ms
feedIcon.gif
1134 ms
spacer.gif
1134 ms
highlight.jpg
1860 ms
daily.png
1652 ms
weekly.png
1652 ms
monthly.png
1660 ms
filter.png
1899 ms
home.png
2163 ms
left.png
2167 ms
right.png
2168 ms
all.js
44 ms
bg_header.jpg
3993 ms
btn_home.jpg
2638 ms
btn_submitevent.jpg
2684 ms
btn_searchevent.jpg
2949 ms
btn_newsletter.jpg
2952 ms
search_bg.jpg
2689 ms
ca-pub-0301340177524142.js
134 ms
zrt_lookup.html
129 ms
show_ads_impl.js
72 ms
magnet_vgeneric.jpg
63 ms
blank.gif
61 ms
blank.gif
61 ms
27.gif
61 ms
transparent_orange_go.gif
60 ms
ch_blu.jpg
3120 ms
ga.js
96 ms
185 ms
xd_arbiter.php
85 ms
xd_arbiter.php
188 ms
ads
332 ms
osd.js
96 ms
ads
337 ms
ping
132 ms
getAllAppDefault.esi
137 ms
__utm.gif
27 ms
ads
244 ms
getSegment.php
225 ms
checkOAuth.esi
6 ms
11831416870184104570
157 ms
abg.js
46 ms
m_js_controller.js
67 ms
googlelogo_color_112x36dp.png
156 ms
386158255489099051
105 ms
906841368827296146
87 ms
s
81 ms
x_button_blue2.png
87 ms
t.dhj
98 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
11 ms
t.dhj
24 ms
cm
21 ms
26 ms
s-3271.xgi
22 ms
hbpix
22 ms
14 ms
pixel
17 ms
2981
18 ms
52154.gif
6 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
17 ms
buttons.ab966a004186897711de4a5ed256c924.css
17 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
13 ms
st.1188278743c14064d5e8ae56c8ada29c.js
15 ms
activeview
16 ms
activeview
26 ms
whatshappening.sg accessibility score
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
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
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.
whatshappening.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
whatshappening.sg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatshappening.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 Whatshappening.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.
whatshappening.sg
Open Graph description is not detected on the main page of Whatshappening. 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: