Your Website Score is

Similar Ranking

49
ONLINE APOTHEKE FÜR DEUTSCHLAND ▷ SHOP APOTHEKE
shop-apotheke.com
49
WEATHER - AUSTRALIA 7 DAY FORECASTS AND WEATHER RADAR - WEATHERZONE
weatherzone.com.au
49
LES VENTES PRIVÉES DE GRANDES MARQUES AVEC SHOWROOMPRIVE
showroomprive.com
49
UNIVERSITY OF JOHANNESBURG
uj.ac.za
49
SHOPGOODWILL.COM
shopgoodwill.com
49
ALLDATASHEET.COM - DATASHEET SEARCH SITE FOR ELECTRONIC COMPONENTS AND SEMICONDUCTORS AND OTHER SEMICONDUCTORS.
alldatasheet.com
49
ETEXTBOOKS | RENT OR BUY ONLINE TEXTBOOKS | VITALSOURCE
vitalsource.com

Latest Sites

23
❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !
baophong.vn
51
ONE MORE STEP
seeking.com
86
MEGOGO.NET - ФИЛЬМЫ И ТЕЛЕКАНАЛЫ ОНЛАЙН
megogo.net
59
MANOMANO : A--- EN LIGNE BRICOLAGE, RÉNOVATION ET JARDINAGE
manomano.fr
91
TECHTUDO - A TECNOLOGIA DESCOMPLICADA.
techtudo.com.br
70
AGILE PROJECT MANAGEMENT | PIVOTAL TRACKER
pivotaltracker.com
31
MOTORPLUS - PORTAL BERITA MOTOR PERTAMA DAN TERKINI
motorplus-online.com

Top Technologies

Nginx
Web Servers
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

49 cars.co.za Last Updated: 9 months

Success 62% of passed verification steps
Warning 23% of total warning
Errors 15% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 78%
Best Practices Desktop Score 77%
SEO Desktop Score 82%
Progressive Web App Desktop Score 19%
Performance Mobile Score 32%
Best Practices Mobile Score 77%
SEO Mobile Score 85%
Progressive Web App Mobile Score 30%
Page Authority Authority 50%
Domain Authority Domain Authority 60%
Moz Rank 5.0/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 74 Characters
CARS FOR SALE IN SOUTH AFRICA, BUY NEW & USED CARS ONLINE - CARS.CO.ZA
Meta Description 177 Characters
Buying a new or used car online is simple with Cars.co.za - South Africa's leading car advertising website, with thousands of new and second hand cars for sale countrywide.
Effective URL 22 Characters
https://www.cars.co.za
Excerpt Page content
Cars for sale in South Africa, Buy new & used cars online - Cars.co.za Buy Car Used Cars New Car Buyer's Guide New Car Specs & Test Drives Compare New Cars Car Alerts Car Specials Se...
Keywords Cloud Density
cars45 review14 used13 finance10 search8 cape7 find7 sale7 information6 insurance6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
cars 45
review 14
used 13
finance 10
search 8
cape 7
find 7
sale 7
information 6
insurance 6
Google Preview Your look like this in google search result
CARS FOR SALE IN SOUTH AFRICA, BUY NEW & USED CARS ONLIN
https://www.cars.co.za
Buying a new or used car online is simple with Cars.co.za - South Africa's leading car advertising website, with thousands of new and second hand
Robots.txt File Detected
Sitemap.xml File Detected
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 2019-03-21 / 1 year
Create on: 1996-03-21 / 24 years
Expires on: 2020-03-21 / 6 months 1 days

xneelo (Pty) Ltd ,CA
Registrar Name: REDACTED
Registrar URL: https://xneelo.co.za/
Registrar Phone: REDACTED
Registrar Email: Please
Registrar Address: REDACTED , REDACTED

REDACTED
Admin Organization: REDACTED
Admin Email: Please
Admin Phone: REDACTED
Admin Address: REDACTED, REDACTED

Nameservers
ns2.host-h.net
ns1.dns-h.com
ns1.host-h.net
Page Size Code & Text Ratio
Document Size: ~51.37 KB
Code Size: ~37.48 KB
Text Size: ~13.88 KB Ratio: 27.02%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Avoid chaining critical requests 11 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 765 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 102 requests • 1,614 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Use video formats for animated content Potential savings of 67 KB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Serve static assets with an efficient cache policy 23 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 2.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 12.3 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 20 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused CSS Potential savings of 39 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 8 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
User Timing marks and measures 17 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Reduce server response times (TTFB) Root document took 1,830 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 310 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimize third-party usage Third-party code blocked the main thread for 30 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 98 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Properly size images Potential savings of 37 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.5 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 2.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 1,614 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Mobile

Mobile Screenshot
Avoid multiple page redirects Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Reduce server response times (TTFB) Root document took 1,240 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,740 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce the impact of third-party code Third-party code blocked the main thread for 660 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 1,140 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 4.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Speed Index 9.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 11.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 1,205 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 6.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 2.7 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 791 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
First Meaningful Paint 2.7 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 117 requests • 1,205 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 25 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 330 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 12.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Page load is not fast enough on mobile networks Interactive at 12.6 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 110 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
First Contentful Paint (3G) 5249 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Document uses legible font sizes 95.72% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Remove unused CSS Potential savings of 37 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Wed, 01 Jan 2020 23:31:04 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Set-Cookie: __cfduid=dbbea76446756460398e6c1bc6fe4c3e81577921464; expires=Fri, 31-Jan-20 23:31:04 GMT; path=/; domain=.cars.co.za; HttpOnly; SameSite=Lax; Secure
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store, must-revalidate
X-Expire-At: Wed, 01 Jan 2020 23:36:00 GMT
X-TLS: 1
X-UA-Device: pc
X-Forwarded-Proto: https
Via: 1.1 varnish
Age: 0
X-Served-By: cache-jfk8142-JFK
X-Cache: HIT
X-Cache-Hits: 1
X-Timer: S1577921465.897518,VS0,VE1
Vary: X-Requested-With,Accept-Encoding, X-UA-Device
Set-Cookie: __uzma=253eb63c81adda04e9349c78568d791e71ce3ca8;Max-Age=315360000;Path=/
Set-Cookie: __uzmb=1577921465;Max-Age=315360000;Path=/
Set-Cookie: __uzmc=852901012980;Max-Age=315360000;Path=/
Set-Cookie: __uzmd=1577921465;Max-Age=315360000;Path=/
Set-Cookie: __uzdbm_a=c5342786-bb66-dc0b-0d6b-84c4b51290cc;Path=/
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
CF-RAY: 54e848e3792fcce2-EWR
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome