10 sec in total
37 ms
9.5 sec
493 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 37 ms and then it took 10 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
Value4.8 s
12/100
10%
Value4.9 s
28/100
25%
Value15.8 s
0/100
10%
Value1,870 ms
9/100
30%
Value0.02
100/100
15%
Value14.4 s
9/100
10%
37 ms
493 ms
312 ms
292 ms
653 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 85% of them (104 requests) were addressed to the original Oldman.sg, 11% (14 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Keyreply.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Oldman.sg.
Page size can be reduced by 149.4 kB (13%)
1.1 MB
980.1 kB
In fact, the total size of Oldman.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. Javascripts take 498.6 kB which makes up the majority of the site volume.
Potential reduce by 133.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. 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 133.0 kB or 85% of the original size.
Potential reduce by 65 B
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. OLDMAN images are well optimized though.
Potential reduce by 9.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 6.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 has all CSS files already compressed.
Number of requests can be reduced by 89 (90%)
99
10
The browser has sent 99 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 65 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
oldman.sg
37 ms
www.oldman.sg
493 ms
1702016675-css0028642887e8f3353553c9dbc970f6abbbfa1b405502588a5cce071ed6a1c.css
312 ms
1702016675-cssf368d67a1c2c843ba6c6ec02ba4e56ee9f5e6d4233039c916a289826bbcc7.css
292 ms
1702016675-cssf9ea4290931717a9869e8e93e4e3f2c3d37d25f9afa41e3c2cf70fe1abd5b.css
653 ms
1702016675-cssed90ef02d8e02bdd06900a68cff027ba8e68049158c7a3e5ef69b993d82dd.css
284 ms
1702016675-css87f3e26f66dab72c0d00a9d84f6ae36412244081b2200e63fa1763759658b.css
1735 ms
1702016675-css03db4277ae546fd13824324f8a44dae6af7d91994f7ba3e581b8d87d398e6.css
1676 ms
1702016675-css2fa174d6e0fd9d407982f99b78bc59f9a1ca248298da569de6ce95e3c5808.css
564 ms
1702016675-cssbe8f8757fe7fb02b9c0832d19c2f3ece4538283b3e488bf614a0f03450833.css
2680 ms
1702016675-css46cacc7c2bb95f8d5268d6af131e4ac9bbdded3c9a866301cd5c528910574.css
2670 ms
1702016675-css4a3a4948f8bb7bb9abc4abfbecca41925b596c83da77f22fa4837d2db77f1.css
2668 ms
1702016675-css84febccbb1fb4423ac27b8b72b1ee74f6fecb5d0721f464fefa733243cb5c.css
2675 ms
1702016675-cssb61fe097658b170afd4fbdd06614fe9d207744b79644bf770c3ae20cd5a66.css
3596 ms
1702016675-css673759330eb2e13046138c15b1725863df8180030d95bd2d091185b6e6f00.css
3694 ms
1702016675-css38daec594af9790b075bb8a1e0e03744abeef395dd3d51b97ae45a9c01a17.css
3714 ms
1702016675-css5ece56cf0516d0b9a8d24f7e3ac584aa9f87a5ed802f86cadbb19fc82da81.css
3782 ms
1702016675-cssc88daf09e73679583c5380ce7b80d263c5d48a2d07ffc3296ecd35455eafc.css
3726 ms
1702016675-cssfb6c7f39522562dc57877358b2c1a128791eeee81d0673cbe056edb783549.css
3725 ms
1702016675-css9122b1ad7437a419bd3a7e7e9231786d1aaa471e1f16ab9570fe4b5a30dd6.css
3888 ms
1702016675-csse31e5f44cd4c6ec7499318df0d8b5218aa8b23203ae3058dfe73c33d6125e.css
4735 ms
1702016675-css089e2124b73741df49ad7dbca9bd498dabde809832af333b311ebc0395ad1.css
4746 ms
jquery.min.js
4012 ms
jquery-migrate.min.js
4005 ms
jquery.themepunch.tools.min.js
4914 ms
jquery.themepunch.revolution.min.js
4857 ms
jquery.blockUI.min.js
4300 ms
add-to-cart.min.js
4285 ms
js.cookie.min.js
4543 ms
woocommerce.min.js
4850 ms
woocommerce-add-to-cart.js
4849 ms
select2.full.min.js
5004 ms
jquery.json.min.js
5021 ms
gravityforms.min.js
5110 ms
placeholders.jquery.min.js
5127 ms
js
64 ms
widget.js
61 ms
email-decode.min.js
4830 ms
1702016675-cssc3a732780f0bb1fcd21882cea91c0d23fe15769b0674034d853fb400ac1d8.css
5169 ms
js
120 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
75 ms
1702016675-css74817b86266bd5e47b5769c077da77eeda28d26e2c342e359af1ae30df264.css
5185 ms
widget.js
90 ms
1702016675-cssa5b8bfdc86d44c04f57ba74cf7b41e2cee3d652eda62e194225e19c906b3b.css
5007 ms
1702016675-css08c64a46ef3eba5a067b8d1e25818cf90de634f87cc79d67ea7697080295a.css
5022 ms
1702016675-cssf0df956821817036d087f782b7b958bc3df60bf0ecab2ccb6e0400c25ae39.css
5081 ms
1702016675-cssddaf295c1be58fb93454dd855a63c5c707b7ff4af0eb39db24798f0f29ab6.css
4853 ms
countUp.js
4806 ms
jquery.scrollify.min.js
4578 ms
script.js
3798 ms
core.min.js
2942 ms
tabs.min.js
3011 ms
accordion.min.js
3016 ms
mediaelement-and-player.min.js
3075 ms
mediaelement-migrate.min.js
2233 ms
wp-mediaelement.min.js
2200 ms
jquery.appear.js
2229 ms
modernizr.min.js
2240 ms
hoverIntent.min.js
2298 ms
jquery.plugin.js
2311 ms
jquery.countdown.min.js
2285 ms
owl.carousel.min.js
2227 ms
jquery.mousewheel.min.js
2218 ms
parallax.min.js
2079 ms
easypiechart.js
2099 ms
waypoints.min.js
1910 ms
Chart.min.js
1801 ms
counter.js
1714 ms
absoluteCounter.min.js
1679 ms
fluidvids.min.js
1706 ms
jquery.prettyPhoto.min.js
1816 ms
jquery.nicescroll.min.js
1877 ms
ScrollToPlugin.min.js
1828 ms
jquery.waitforimages.js
1804 ms
jquery.easing.1.3.js
1782 ms
jquery.multiscroll.min.js
1699 ms
webdesignback-1.jpg
77 ms
isotope.pkgd.min.js
1771 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff
31 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff
32 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
88 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
94 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
96 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
96 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff
97 ms
packery-mode.pkgd.min.js
1795 ms
webdesignback-1.jpg
2048 ms
S6uyw4BMUTPHjx4wWA.woff
25 ms
S6u9w4BMUTPHh7USSwiPHw.woff
11 ms
S6u8w4BMUTPHh30AXC-s.woff
13 ms
S6u9w4BMUTPHh6UVSwiPHw.woff
14 ms
S6u9w4BMUTPHh50XSwiPHw.woff
24 ms
jquery.fullPage.min.js
1812 ms
typed.js
2520 ms
jquery.parallax-scroll.js
1683 ms
swiper.min.js
1815 ms
modules.min.js
1827 ms
js_composer_front.min.js
2491 ms
like.js
1756 ms
smush-lazy-load.min.js
1873 ms
vcparticlesbackground.js
1829 ms
particles.min.js
1796 ms
jquery.prettyPhoto.min.js
2569 ms
masonry.pkgd.min.js
1894 ms
owl.carousel.min.js
1886 ms
imagesloaded.pkgd.min.js
1854 ms
underscore.min.js
2804 ms
vc_grid.min.js
1966 ms
akismet-frontend.js
1930 ms
linea-arrows-10.woff
1900 ms
fontawesome-webfont.woff
2092 ms
vc_entypo.woff
2068 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff
16 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
17 ms
portfolio-logos1.jpg
2039 ms
portfolio-logos2.jpg
2045 ms
portfolio-logos3.jpg
2178 ms
portfolio-logos4.jpg
2204 ms
portfolio-logos5.jpg
2148 ms
oldmanmail.png
16 ms
oldmanmail.png
617 ms
language-logos-1.jpg
15 ms
language-logos-1.jpg
310 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 data is detected on the main page of OLDMAN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: