Recogniseandreward.co.nz - SEO Checker

Your Website Score is

Similar Ranking

recogniseandreward.co.nz

SHOP - HEALTH CARE PRICES

health.bestpricedirectory.com.au

Latest Sites

recogniseandreward.co.nz

BLACK BOX PRODUCT REVIEWS

blackboxreviews.co.nz

MOBILE PHONE REPAIR SERVICES | SCREEN REPLACEMENT | IPHONE REPAIR AUCKLAND

techpro.net.nz

LIFE COACH | BUSINESS COACH | CORPORATE WORKSHOPS | BREE LE ROUX

breeleroux.com

HOME ENERGY MANAGEMENT SERVICE | POWERGENIUS

powergenius.net

BLACK BOX MARKET

blackboxmarket.co.nz

WP USED CARS – JUST ANOTHER WORDPRESS SITE

wp.usedcarsforsale.nz

Top Technologies

CloudFlare

CDN

WordPress

CMS

PHP

Programming Languages

Google Font API

Font Scripts

jQuery

JavaScript Frameworks

WooCommerce

Ecommerce

Font Awesome

Font Scripts

Shopify

Ecommerce

React

JavaScript Frameworks

Lo-dash

JavaScript Frameworks

11 recogniseandreward.co.nz Last Updated: 3 months

Success 47% of passed verification steps

Warning 30% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 65%

Best Practices Desktop Score 79%

SEO Desktop Score 92%

Progressive Web App Desktop Score 30%

Performance Mobile Score 18%

Best Practices Mobile Score 79%

SEO Mobile Score 90%

Progressive Web App Mobile Score 32%

Page Authority Authority 24%

Domain Authority Domain Authority 18%

Moz Rank 2.4/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 197 Characters

Meta Description 179 Characters

Personalised corporate Gifts | Personalised Corporate Gifts | Company Branded Merchandise & Apparel | PPE | Branded Stationary, hand wrapped & delivered. NZ & Austalia

Effective URL 32 Characters

https://recogniseandreward.co.nz

Excerpt Page content

Keywords Cloud Density

contact6 products6 brands5 cart4 branded4 apparel4 gifts4 reward4 about3 merchandise3

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

Keyword	Freq	Title	Desc	Domain	H1	H2
contact	6
products	6
brands	5
cart	4
branded	4
apparel	4
gifts	4
reward	4
about	3
merchandise	3

Google Preview Your look like this in google search result

BRANDED MERCHANDISE MADE EASY! GIFTS | BRANDING | BRANDED AP

https://recogniseandreward.co.nz

Personalised corporate Gifts | Personalised Corporate Gifts | Company Branded Merchandise & Apparel | PPE | Branded Stationary, hand wrapped &

Robots.txt File Detected

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

Sitemap.xml File Detected

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

Page Size Code & Text Ratio

Document Size: ~82.68 KB

Code Size: ~55.29 KB

Text Size: ~27.39 KB Ratio: 33.13%

Estimation Traffic and Earnings

Unique Visits

Daily

Pages Views

Daily

Income

Daily

224

Unique Visits

Monthly

399

Pages Views

Monthly

Income

Monthly

2,592

Unique Visits

Yearly

4,704

Pages Views

Yearly

Income

Yearly

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

PWA - Manifest

Manifest is not valid

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

Desktop

Max Potential First Input Delay 170 ms

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

First Meaningful Paint 1.5 s

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

Time to Interactive 3.9 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Avoid long main-thread tasks 5 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

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

Eliminate render-blocking resources Potential savings of 1,660 ms

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

First Contentful Paint 1.5 s

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

Remove unused CSS Potential savings of 179 KiB

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 static assets with an efficient cache policy 60 resources found

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

Properly size images Potential savings of 18 KiB

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

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

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

Minify JavaScript Potential savings of 11 KiB

Minifying JavaScript files can reduce payload sizes and script parse time

Defer offscreen images Potential savings of 11 KiB

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

Avoids large JavaScript libraries with smaller alternatives 0 large libraries found

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size

Serve images in next-gen formats Potential savings of 34 KiB

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

Avoids enormous network payloads Total size was 1,494 KiB

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

Reduce initial server response time Root document took 1,240 ms

Keep the server response time for the main document short because all other requests depend on it

Cumulative Layout Shift 0.033

Cumulative Layout Shift measures the movement of visible elements within the viewport

Largest Contentful Paint 2.1 s

Largest Contentful Paint marks the time at which the largest text or image is painted

Avoid serving legacy JavaScript to modern browsers Potential savings of 13 KiB

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers

First CPU Idle 2.9 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/).

Minimizes main-thread work 1.9 s

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

Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected

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

Minify CSS Potential savings of 14 KiB

Minifying CSS files can reduce network payload sizes

Avoids an excessive DOM size 547 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)

User Timing marks and measures 4 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Remove unused JavaScript Potential savings of 565 KiB

Remove unused JavaScript to reduce bytes consumed by network activity

Avoid large layout shifts 5 elements found

These DOM elements contribute most to the CLS of the page.

Speed Index 3.6 s

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

Keep request counts low and transfer sizes small 93 requests • 1,494 KiB

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

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

Total Blocking Time 100 ms

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

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

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

Largest Contentful Paint element 1 element found

This is the largest contentful element painted within the viewport

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

Mobile

Avoids an excessive DOM size 547 elements

Eliminate render-blocking resources Potential savings of 5,350 ms

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

First Contentful Paint (3G) 10403 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

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

Avoid large layout shifts 5 elements found

These DOM elements contribute most to the CLS of the page.

First CPU Idle 13.1 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/).

Time to Interactive 15.7 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Tap targets are not sized appropriately 72% 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

Reduce initial server response time Root document took 870 ms

Keep the server response time for the main document short because all other requests depend on it

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

First Contentful Paint 5.3 s

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

Serve static assets with an efficient cache policy 60 resources found

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

Avoids enormous network payloads Total size was 1,542 KiB

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

First Meaningful Paint 5.6 s

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

Avoid chaining critical requests 47 chains found

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

Preload key requests Potential savings of 660 ms

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

Defer offscreen images Potential savings of 11 KiB

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

Avoid long main-thread tasks 18 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

Estimated Input Latency 250 ms

Reduce JavaScript execution time 3.3 s

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

Minify JavaScript Potential savings of 11 KiB

Minifying JavaScript files can reduce payload sizes and script parse time

Serve images in next-gen formats Potential savings of 69 KiB

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

Total Blocking Time 1,110 ms

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

Avoids large JavaScript libraries with smaller alternatives 0 large libraries found

Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size

Remove unused CSS Potential savings of 178 KiB

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

Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected

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

Minimize main-thread work 6.5 s

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

Largest Contentful Paint 5.3 s

Largest Contentful Paint marks the time at which the largest text or image is painted

Largest Contentful Paint element 1 element found

This is the largest contentful element painted within the viewport

Max Potential First Input Delay 670 ms

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

Keep request counts low and transfer sizes small 93 requests • 1,542 KiB

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

Document uses legible font sizes 99.21% 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

Minify CSS Potential savings of 14 KiB

Minifying CSS files can reduce network payload sizes

Avoid serving legacy JavaScript to modern browsers Potential savings of 13 KiB

Cumulative Layout Shift 0.192

Cumulative Layout Shift measures the movement of visible elements within the viewport

Page load is not fast enough on mobile networks Interactive at 15.7 s

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

Speed Index 11.7 s

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

Remove unused JavaScript Potential savings of 582 KiB

Remove unused JavaScript to reduce bytes consumed by network activity

User Timing marks and measures 4 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you

Title Website

Warning! Your title is not optimized

Description Website

Warning! Your description is not optimized

Robots.txt

Congratulations! Your site have a robots.txt file

Sitemap.xml

Congratulations! We've found a sitemap file for your website

SSL Secure

Congratulations! Your site have Support to HTTPS

Headings

Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines

Blacklist

Congratulations! Your site is not listed in a blacklist

W3C Validator

Warning! Your site have errors W3C

Accelerated Mobile Pages (AMP)

Warning! Your site not have AMP Version

Domain Authority

Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.

GZIP Compress

Warning! Your site not is compressed, this can make slower response for the visitors

Favicon

Congratulations! Your website appears to have a favicon.

Broken Links

Congratulations! You not have broken links View links

First 16 Links	Relationship	HTTP Status
Home	Internal Link	200
About us	Internal Link	200
Brands	Internal Link	200
Products	Internal Link	200
Branded Merchandise & Apparel	Internal Link	200
Gifts	Internal Link	200
Contact	Internal Link	200
https://recogniseandreward.co.nz	Internal Link	200
Sign In	Internal Link	200
Register	Internal Link	200
Cart 0 items for $0.00	Internal Link	200
http://recogniseandreward.co.nz/www.logoline.co.nz	Internal Link	301
Our Brands	Internal Link	301
Blog	Internal Link	200
https://recogniseandreward.co.nz/?responsive=off	Internal Link	302
Lost Password?	Internal Link	200

Alexa Rank

99,999,999

Global Rank

99,999,999

Traffic

Search

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Date: Thu, 22 Oct 2020 21:51:11 GMT
Server: Apache/2
X-Powered-By: PHP/7.0.33
P3P: CP="ALL DSP NID CURa ADMa DEVa HISa OTPa OUR NOR NAV DEM"
X-Pingback: https://recogniseandreward.co.nz/xmlrpc.php
Link: ; rel="https://api.w.org/", ; rel=shortlink
Upgrade: h2,h2c
Connection: Upgrade
Vary: User-Agent
Content-Type: text/html; charset=UTF-8

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	recogniseandreward.co.nz	103.49.172.142	IN	280
NS	recogniseandreward.co.nz	ns1.nzdns.net.nz	IN	300
NS	recogniseandreward.co.nz	ns2.nzdns.net.nz	IN	300
MX	recogniseandreward.co.nz	recogniseandreward-co-nz.mail.protection.outlook.com	IN	300
TXT	recogniseandreward.co.nz	v=spf1 a mx ip4:103.49.172.162 ip4:103.49.172.142 ~all	IN	300

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

11 recogniseandreward.co.nz Last Updated: 3 months

Desktop

Mobile

Estimation Traffic and Earnings

Technologies

Sign up for see all features and reviews about this site

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Alexa Rank

99,999,999

99,999,999

Information Server

About Us

Contact Info

Follow Us