17.5 sec in total
3 sec
13.7 sec
764 ms
Click here to check amazing Otua content. Otherwise, check out these important facts you probably never knew about otua.sg
Otua Auto is a Singapore based car dealership. Sell your used car or resale motorcycle at the highest possible price. Contact us now to know the valuation of your car in just 24hrs.
Visit otua.sgWe analyzed Otua.sg page load time and found that the first response time was 3 sec and then it took 14.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
otua.sg performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value9.2 s
1/100
25%
Value11.7 s
4/100
10%
Value1,000 ms
27/100
30%
Value0.174
69/100
15%
Value9.4 s
31/100
10%
3028 ms
1015 ms
1470 ms
1012 ms
991 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 84% of them (51 requests) were addressed to the original Otua.sg, 5% (3 requests) were made to S.w.org and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (7.4 sec) belongs to the original domain Otua.sg.
Page size can be reduced by 695.5 kB (71%)
973.3 kB
277.8 kB
In fact, the total size of Otua.sg main page is 973.3 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. 45% of websites need less resources to load. CSS take 561.4 kB which makes up the majority of the site volume.
Potential reduce by 72.1 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 72.1 kB or 84% of the original size.
Potential reduce by 811 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. Otua images are well optimized though.
Potential reduce by 139.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 139.5 kB or 61% of the original size.
Potential reduce by 483.0 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. Otua.sg needs all CSS files to be minified and compressed as it can save up to 483.0 kB or 86% of the original size.
Number of requests can be reduced by 48 (84%)
57
9
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otua. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
otua.sg
3028 ms
wp-emoji-release.min.js
1015 ms
609xl.css
1470 ms
609xl.css
1012 ms
609xk.css
991 ms
609xk.css
981 ms
609xk.css
1190 ms
609xk.css
2141 ms
609xk.css
1988 ms
609xk.css
2746 ms
post-8.css
1937 ms
609xk.css
2814 ms
609xk.css
2686 ms
post-192.css
2889 ms
post-121.css
2905 ms
post-175.css
3111 ms
post-1929.css
3635 ms
post-409.css
3680 ms
609xk.css
4200 ms
609xk.css
3842 ms
post-238.css
3843 ms
post-241.css
4066 ms
609xk.css
4550 ms
wp-polyfill.min.js
5118 ms
index.js
4916 ms
smush-lazy-load.min.js
4821 ms
wp-embed.min.js
5034 ms
jquery.min.js
5700 ms
jquery-migrate.min.js
5568 ms
jquery.smartmenus.min.js
6011 ms
imagesloaded.min.js
5848 ms
webpack.runtime.min.js
6035 ms
frontend-modules.min.js
6571 ms
jquery.sticky.min.js
6496 ms
frontend.min.js
7400 ms
core.min.js
7044 ms
v652eace1692a40cfa3763df669d7439c1639079717194
70 ms
dialog.min.js
6956 ms
waypoints.min.js
6025 ms
share-link.min.js
6474 ms
swiper.min.js
7300 ms
frontend.min.js
7399 ms
preloaded-elements-handlers.min.js
6993 ms
gtm.js
173 ms
MBenz-G-Class.jpg
4211 ms
fa-brands-400.woff
4453 ms
analytics.js
59 ms
recorder.js
119 ms
fbevents.js
26 ms
2324589914493643
109 ms
collect
13 ms
fa-solid-900.woff
4506 ms
wp-polyfill-fetch.min.js
3949 ms
wp-polyfill-dom-rect.min.js
4051 ms
wp-polyfill-url.min.js
4383 ms
wp-polyfill-formdata.min.js
4263 ms
1f44d-1f3fb.svg
18 ms
1f60c.svg
20 ms
1f44d-1f3fc.svg
19 ms
logo.svg
966 ms
smush-lazyloader-3.gif
961 ms
otua.sg accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
otua.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
Browser errors were logged to the console
Page has valid source maps
otua.sg 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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otua.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 Otua.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.
otua.sg
Open Graph data is detected on the main page of Otua. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: