13.1 sec in total
2.1 sec
10.5 sec
510 ms
Click here to check amazing OLDMAN content for Singapore. Otherwise, check out these important facts you probably never knew about oldman.sg
We are a Singapore based web design company with passionate designers and results driven digital marketing specialists.
Visit oldman.sgWe analyzed Oldman.sg page load time and found that the first response time was 2.1 sec and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
oldman.sg performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value6.3 s
11/100
25%
Value14.6 s
1/100
10%
Value1,330 ms
17/100
30%
Value0.021
100/100
15%
Value14.9 s
8/100
10%
2071 ms
12 ms
38 ms
44 ms
48 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 77% of them (71 requests) were addressed to the original Oldman.sg, 14% (13 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Oldman.sg.
Page size can be reduced by 1.3 MB (68%)
1.9 MB
604.6 kB
In fact, the total size of Oldman.sg main page is 1.9 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. CSS take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 41.3 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 41.3 kB or 82% of the original size.
Potential reduce by 88.2 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. Obviously, OLDMAN needs image optimization as it can save up to 88.2 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 223.1 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 223.1 kB or 70% of the original size.
Potential reduce by 958.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. Oldman.sg needs all CSS files to be minified and compressed as it can save up to 958.9 kB or 91% of the original size.
Number of requests can be reduced by 36 (47%)
77
41
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OLDMAN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.oldman.sg
2071 ms
ga.js
12 ms
css
38 ms
css
44 ms
css
48 ms
sociable.css
500 ms
style.css
508 ms
woocommerce-layout.css
499 ms
woocommerce.css
503 ms
style.css
506 ms
global.css
518 ms
galleria.flamingo.css
740 ms
js_composer.css
1482 ms
jquery.js
1237 ms
jquery-migrate.min.js
747 ms
sociable.js
747 ms
vuible.js
764 ms
addtofavorites.js
984 ms
plusone.js
55 ms
__utm.gif
14 ms
jquery.form.min.js
962 ms
scripts.js
962 ms
tabs.js
976 ms
jquery.blockUI.min.js
1204 ms
woocommerce.min.js
1209 ms
jquery.cookie.min.js
1208 ms
cart-fragments.min.js
1223 ms
scripts.js
2204 ms
hoverIntent.js
1490 ms
superfish.js
2183 ms
jquery.cycle.lite.js
1491 ms
custom.js
1720 ms
comment-reply.min.js
1696 ms
js_composer_front.js
1702 ms
wp-emoji-release.min.js
1685 ms
style.css
1481 ms
plusone.js
156 ms
cb=gapi.loaded_0
95 ms
oldman.png
424 ms
nabil-042.jpg
1786 ms
back3.jpg
2543 ms
responsive-portfolio-design1-200x200.png
424 ms
wordpress-theme-seo-friendly1-200x200.png
932 ms
portfolio-freelance-media1-200x200.png
444 ms
responsive-design1-200x200.png
555 ms
wordpress-themes-for-agencies-200x200.png
563 ms
websites-for-feelance-200x200.png
677 ms
retina-wordpress-theme-code1-200x200.png
801 ms
page-builder-composer-bike1-200x200.png
809 ms
microsoft.jpg
1177 ms
keppelland.jpg
1052 ms
streetdirectory.jpg
1303 ms
veeam.jpg
2202 ms
acronis.jpg
1301 ms
catech.jpg
1954 ms
wd.jpg
1563 ms
moneyline.jpg
1562 ms
contactone.jpg
1826 ms
abwin.jpg
1825 ms
ingrammicro.jpg
2275 ms
ixix.jpg
2319 ms
stone-forest-it.jpg
2080 ms
sis1.jpg
2201 ms
reddot.jpg
2336 ms
pod.jpg
2446 ms
nec.jpg
2447 ms
ki-mono.jpg
2522 ms
HLS.jpg
2565 ms
edumatters.jpg
2579 ms
december.jpg
2700 ms
dcg.jpg
2704 ms
cyan-sys.jpg
2728 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
21 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
64 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
62 ms
8KhZd3VQBtXTAznvKjw-ky3USBnSvpkopQaUR-2r7iU.ttf
62 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
61 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
61 ms
1ImRNPx4870-D9a1EBUdPC3USBnSvpkopQaUR-2r7iU.ttf
62 ms
PKCRbVvRfd5n7BTjtGiFZC3USBnSvpkopQaUR-2r7iU.ttf
62 ms
BfQP1MR3mJNaumtWa4Tizg.ttf
62 ms
zR-6QGMCFX5j-6nbH_HpIQ.ttf
62 ms
fontawesome-webfont.woff
2632 ms
admin-ajax.php
3328 ms
galleria.flamingo.min.js
2401 ms
QQT_AUSp4AV4dpJfIN7U5FwRGS1J0uDbqVT85dREjI0.ttf
8 ms
n6RTCDcIPWSE8UNBa4k-DLGMqOskSJahibCG-vhG9Ug.ttf
6 ms
5Ywdce7XEbTSbxs__4X1_AzXKzPdQ5IRTaDVrbjtIFE.ttf
8 ms
culinaryion.jpg
2521 ms
audacious.jpg
2518 ms
wedding-sweet.jpg
2480 ms
woocommerce-smallscreen.css
249 ms
oldman.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
oldman.sg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
oldman.sg SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oldman.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 Oldman.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.
oldman.sg
Open Graph description is not detected on the main page of OLDMAN. 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: