Trademe.co.nz - SEO Checker

Your Website Score is

Similar Ranking

DOW JONES – BUSINESS & FINANCIAL NEWS, ANALYSIS & INSIGHT

dowjones.com

THE OFFICIAL HOME OF YIFY MOVIES TORRENT DOWNLOAD - YTS

yts.lt

GIBRALTAR CHRONICLE

chronicle.gi

UI KITS, ICONS, TEMPLATES, THEMES AND MORE - UPLABS

uplabs.com

NOTICIAS, DEPORTES Y ESPECTÁCULO DE GUATEMALA Y EL MUNDO | PUBLINEWS

publinews.gt

PAYSCALE - SALARY COMPARISON, SALARY SURVEY, SEARCH WAGES

payscale.com

PÁGINAS - INICIO

isciii.es

Latest Sites

START BITCOIN MINING FOR FREE, NO FEES, DAILY PAYOUTS: UNMINED.IO

unmined.io

TALENT DESIRE : EXCEED YOUR POTENTIAL...

talentdesire.com

BITCOINS43 | EARN FREE BITCOINS EVERY DAY

bitcoins43.com

FACEBOOK - LOG IN OR SIGN UP

facebook.com

INVESTISSEMENTVIVA

investissementviva.com

sharenow126.com

BUY STROMECTOL - IVERMECTIN ONLINE

ivermectin24h.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

58 trademe.co.nz Last Updated: 1 year

Success 54% of passed verification steps

Warning 23% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 62%

Best Practices Desktop Score 69%

SEO Desktop Score 91%

Progressive Web App Desktop Score 31%

Performance Mobile Score 42%

Best Practices Mobile Score 85%

SEO Mobile Score 99%

Progressive Web App Mobile Score 48%

Page Authority Authority 56%

Domain Authority Domain Authority 78%

Moz Rank 5.6/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 74 Characters

BUY ONLINE AND SELL WITH NZ'S #1 AUCTION & CLASSIFIEDS SITE | TRADE ME

Meta Description 172 Characters

Want to buy or sell? Head to Trade Me, NZ’s biggest & most popular auction & classifieds site, with thousands of new & used items in a wide range of categories.

Effective URL 25 Characters

https://www.trademe.co.nz

Excerpt Page content

Buy online and sell with NZ's #1 auction & classifieds site | Trade Me Satellite sites Trade Me ...

Keywords Cloud Density

reserve64 watchlist63 adding60 watching60 auckland47 current37 price23 start23 canterbury19 plenty19

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
reserve	64
watchlist	63
adding	60
watching	60
auckland	47
current	37
price	23
start	23
canterbury	19
plenty	19

Google Preview Your look like this in google search result

BUY ONLINE AND SELL WITH NZ'S #1 AUCTION & CLASSIFIEDS S

https://www.trademe.co.nz

Want to buy or sell? Head to Trade Me, NZ’s biggest & most popular auction & classifieds site, with thousands of new & used items in a wid

Robots.txt File Detected

http://trademe.co.nz/robots.txt

Sitemap.xml File No Found

http://trademe.co.nz/sitemap.xml

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: 1970-01-01 / 51 years

Create on: 1970-01-01 / 51 years

Expires on: 1970-01-01 / 622 months 25 days

Page Size Code & Text Ratio

Document Size: ~308.52 KB

Code Size: ~163.6 KB

Text Size: ~144.93 KB Ratio: 46.97%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

Google Tag Manager

Tag Managers

PWA - Manifest

Manifest is not valid

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

Desktop

JavaScript execution time 0.8 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

Defer offscreen images Potential savings of 210 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Properly size images Potential savings of 59 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 4.3 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 2.5 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,854 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimizes main-thread work 1.7 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.8 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 5 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 23 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

Avoid an excessive DOM size 3,290 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)

Minify JavaScript Potential savings of 14 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 1.1 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 155 requests • 1,854 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 32 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 100 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 3.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 on simulated mobile network at 15.5 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 128 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

Uses deprecated APIs 1 warning found

Deprecated APIs will eventually be removed from the browser

Serve images in next-gen formats Potential savings of 255 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

Reduce server response times (TTFB) Root document took 1,920 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 530 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Efficiently encode images Potential savings of 44 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 40 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 50 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Mobile

Serve static assets with an efficient cache policy 51 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 1,870 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 18.0 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 18.0 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 1,110 ms

First Contentful Paint (3G) 2509 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 not sized appropriately 98% 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 100% 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

Serve images in next-gen formats Potential savings of 114 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

Avoid multiple page redirects Potential savings of 780 ms

Redirects introduce additional delays before the page can be loaded

User Timing marks and measures 30 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 2,970 ms

Time To First Byte identifies the time at which your server sends a response

Reduce the impact of third-party code Third-party code blocked the main thread for 1,060 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 5,230 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 10.9 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

Defer offscreen images Potential savings of 671 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Speed Index 13.9 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 1.7 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 2,280 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 14.4 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 1.3 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 7 chains found

Avoid an excessive DOM size 2,650 elements

Minify JavaScript Potential savings of 6 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 1.3 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 107 requests • 2,280 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

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
Cache-Control: private, must-revalidate, no-cache, no-check
Pragma: no-cache
Content-Length: 330895
Content-Type: text/html; charset=utf-8
Expires: Fri, 03 Mar 2017 10:27:25 GMT
Content-Security-Policy-Report-Only: default-src https: data:; script-src https: data: 'unsafe-inline' 'unsafe-eval'; style-src https: data: 'unsafe-inline'; report-uri https://csp.tmcdn.co.nz/report
Strict-Transport-Security: max-age=31536000
Content-Security-Policy: upgrade-insecure-requests
X-XSS-Protection: 1; report=https://csp.tmcdn.co.nz/report
Referrer-Policy: no-referrer-when-downgrade
x-frame-options: Deny
Set-Cookie: session=%7bC986F066-B5DE-4B32-AADB-D8E94A4019CF%7d; domain=trademe.co.nz; path=/; secure; HttpOnly
P3P: policyref="/w3c/p3p.xml", CP="ALL DSP COR CURa ADMa DEVi CUSi TAIi PSAi PSDi OUR STP"
Date: Thu, 28 Nov 2019 10:27:24 GMT
X-UA-Compatible: IE=Edge
Set-Cookie: TS0141ee74=018feaa5bcd655168244da1a2620495e0640ed9c1d280482ae52eedffea3e0942b05657e5ad92002208a92e2c2bd27484beca87a29; Path=/
Set-Cookie: TS01ae6471=018feaa5bc752d1ffe1749f6e6459d6b6a436f243a280482ae52eedffea3e0942b05657e5ac5d3925a0b93b368f9d2a9ac74dff77e3de0a364fd6245288a5a7b10034c57cd; path=/; domain=trademe.co.nz

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	trademe.co.nz	202.162.73.2	IN	30
NS	trademe.co.nz	ns4.trademe.co.nz	IN	3004
NS	trademe.co.nz	ns2.trademe.co.nz	IN	3004
NS	trademe.co.nz	ns1.trademe.co.nz	IN	3004
NS	trademe.co.nz	ns3.trademe.co.nz	IN	3004
MX	trademe.co.nz	alt3.aspmx.l.google.com	IN	299
MX	trademe.co.nz	alt4.aspmx.l.google.com	IN	299
MX	trademe.co.nz	alt1.aspmx.l.google.com	IN	299
MX	trademe.co.nz	aspmx.l.google.com	IN	299
MX	trademe.co.nz	alt2.aspmx.l.google.com	IN	299
TXT	trademe.co.nz	google-site-verification=JJnDdFiuWaIure4nDwdE8Z8JWb5yPseuEGBbIUhNoKQ	IN	3004
TXT	trademe.co.nz	google-site-verification=aONrYCywZgma9iE1uCjwGK4uju_mxnIRySqkdbAyvXc	IN	3004
TXT	trademe.co.nz	v=spf1 ip4:202.21.128.30/31 ip4:202.162.72.30/31 ip4:202.162.73.30/31 ip4:203.57.145.30/31 ip4:203.57.145.32/28 ip4:202.21.128.32/28 ip4:202.162.72.32/28 ip4:202.162.73.32/28 include:spf0.trademe.co.nz -all	IN	3004
TXT	trademe.co.nz	google-site-verification=NPaXBcuJVX_jBkVG4ni3hTCJZuvwIQzpgCtD7iNfA4g	IN	3004
TXT	trademe.co.nz	8Jr2iiAFDw58Nshh2/JC+5S9jEt39ofCQlV7NNWo3drVJlDHaasGwSiN66TcM6qaciZrdrD/wckqc1JOrkd2QA==	IN	3004

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

58 trademe.co.nz Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Google Tag Manager

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments