11.9 sec in total
28 ms
11.7 sec
175 ms
Visit durian36.com now to see the best up-to-date Durian 36 content for Singapore and also check out these interesting facts you probably never knew about durian36.com
Craving for durian in the wee hours? Fret not – Durian 36 makes late night durian feast possible! We operate 24 hours in Singapore. Find out more.
Visit durian36.comWe analyzed Durian36.com page load time and found that the first response time was 28 ms and then it took 11.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
durian36.com performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value4.9 s
28/100
25%
Value14.8 s
1/100
10%
Value1,370 ms
16/100
30%
Value1.002
2/100
15%
Value11.0 s
21/100
10%
28 ms
1054 ms
1207 ms
67 ms
1795 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 88% of them (37 requests) were addressed to the original Durian36.com, 5% (2 requests) were made to Googletagmanager.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Durian36.com.
Page size can be reduced by 45.4 kB (63%)
71.6 kB
26.2 kB
In fact, the total size of Durian36.com main page is 71.6 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. 30% of websites need less resources to load. Javascripts take 52.9 kB which makes up the majority of the site volume.
Potential reduce by 13.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 13.5 kB or 72% of the original size.
Potential reduce by 32.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 32.0 kB or 60% of the original size.
Number of requests can be reduced by 10 (29%)
34
24
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Durian 36. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
durian36.com
28 ms
durian36.com
1054 ms
www.durian36.com
1207 ms
gtm.js
67 ms
bootstrap.min.css
1795 ms
web-font.css
1084 ms
font-awesome.css
1291 ms
full-slider.css
1298 ms
responsive.css
1086 ms
jquery.fullPage2.css
1047 ms
jquery.js
2568 ms
bootstrap.min.js
2341 ms
jquery.fullPage.js
2629 ms
logo.png
1234 ms
RWSgrouppics1.JPG
2541 ms
slide-logo.png
1017 ms
party-icon.png
1251 ms
in-stored-durian.png
1291 ms
export.png
1274 ms
about_background.jpg
2043 ms
ahyat.png
2506 ms
gsk.png
2501 ms
bakerzia.png
2288 ms
singtel.png
2542 ms
ite.png
3303 ms
thai.png
3558 ms
cecilia.png
4534 ms
zao.png
4588 ms
zhongqing.png
4564 ms
hayu.png
4548 ms
pornsak.png
5503 ms
fb.png
4581 ms
insta.png
5563 ms
footer-logo.png
5555 ms
opensans-semibold-webfont.woff
5844 ms
opensans-regular-webfont.woff
5876 ms
opensans-extrabold-webfont.woff
5891 ms
opensans-bold-webfont.woff
6746 ms
analytics.js
30 ms
collect
13 ms
collect
25 ms
js
53 ms
durian36.com accessibility score
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
durian36.com 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
durian36.com 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
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 Durian36.com 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 Durian36.com 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.
durian36.com
Open Graph description is not detected on the main page of Durian 36. 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: