Tools & Wizards About Us
recogniseandreward.co.nz screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

recogniseandreward.co.nz

Branded Merchandise Made Easy! Gifts | Branding | Branded ApparelPersonalised Corporate Gifts | Company Branded Merchandise & Apparel | PPE | Branded ...

Page Load Speed

6.6 sec in total

First Response

609 ms

Resources Loaded

5.7 sec

Page Rendered

278 ms

recogniseandreward.co.nz screenshot

About Website

Visit recogniseandreward.co.nz now to see the best up-to-date Recogniseandreward content and also check out these interesting facts you probably never knew about recogniseandreward.co.nz

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

Visit recogniseandreward.co.nz

Key Findings

We analyzed Recogniseandreward.co.nz page load time and found that the first response time was 609 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

recogniseandreward.co.nz performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.171

70/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

recogniseandreward.co.nz

609 ms

recogniseandreward.co.nz

1943 ms

style.min.css

392 ms

styles.css

586 ms

ai-search-bar-style.css

587 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 84% of them (46 requests) were addressed to the original Recogniseandreward.co.nz, 7% (4 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Recogniseandreward.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 792.3 kB (15%)

Content Size

5.3 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Recogniseandreward.co.nz main page is 5.3 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. 50% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 84.5 kB

  • Original 102.9 kB
  • After minification 100.8 kB
  • After compression 18.4 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 84.5 kB or 82% of the original size.

Image Optimization

-14%

Potential reduce by 628.9 kB

  • Original 4.6 MB
  • After minification 3.9 MB

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. Obviously, Recogniseandreward needs image optimization as it can save up to 628.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 15.8 kB

  • Original 484.6 kB
  • After minification 483.1 kB
  • After compression 468.8 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.

CSS Optimization

-31%

Potential reduce by 63.1 kB

  • Original 204.3 kB
  • After minification 190.2 kB
  • After compression 141.1 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. Recogniseandreward.co.nz needs all CSS files to be minified and compressed as it can save up to 63.1 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (73%)

Requests Now

48

After Optimization

13

  • Images
  • JavaScript
  • CSS

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Recogniseandreward. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

recogniseandreward.co.nz

recogniseandreward.co.nz

609 ms

recogniseandreward.co.nz

recogniseandreward.co.nz

1943 ms

style.min.css

style.min.css

392 ms

styles.css

styles.css

586 ms

ai-search-bar-style.css

ai-search-bar-style.css

587 ms

codemirror.css

codemirror.css

587 ms

style.css

style.css

1000 ms

js_composer.min.css

js_composer.min.css

985 ms

font-awesome.css

font-awesome.css

588 ms

style.css

style.css

781 ms

css

css

29 ms

css

css

46 ms

responsive.css

responsive.css

784 ms

custom.css

custom.css

781 ms

jquery.min.js

jquery.min.js

787 ms

jquery-migrate.min.js

jquery-migrate.min.js

976 ms

codemirror.min.js

codemirror.min.js

1765 ms

codemirror.js

codemirror.js

1379 ms

xml.js

xml.js

984 ms

css.js

css.js

1172 ms

javascript.js

javascript.js

1180 ms

htmlmixed.js

htmlmixed.js

1180 ms

front-script.js

front-script.js

1181 ms

ai.min.js

ai.min.js

1370 ms

head.js

head.js

1378 ms

css

css

18 ms

hooks.min.js

hooks.min.js

1187 ms

i18n.min.js

i18n.min.js

1187 ms

index.js

index.js

1377 ms

index.js

index.js

1382 ms

feature-tilespace.js

feature-tilespace.js

1382 ms

jquery.sonar.min.js

jquery.sonar.min.js

1384 ms

lazy-load.js

lazy-load.js

1384 ms

plugins.min.js

plugins.min.js

1777 ms

etheme.js

etheme.js

1655 ms

js_composer_front.min.js

js_composer_front.min.js

1655 ms

large-resolution.css

large-resolution.css

197 ms

logo-RecogniseAndReward-RGB-noTag-circle-BLACK-300px.png

logo-RecogniseAndReward-RGB-noTag-circle-BLACK-300px.png

259 ms

tagline-RecogniseAndReward.png

tagline-RecogniseAndReward.png

259 ms

logo.png

logo.png

260 ms

1x1.trans.gif

1x1.trans.gif

259 ms

all.js

all.js

81 ms

small-close.png

small-close.png

198 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVcUwaEQXjM.ttf

28 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVcUwaEQXjM.ttf

56 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVcUwaEQXjM.ttf

61 ms

oY1B8fbBpaP5OX3DtrRYf_Q2BPB1SnfZb3OOnV4H2pmp.ttf

oY1B8fbBpaP5OX3DtrRYf_Q2BPB1SnfZb3OOnV4H2pmp.ttf

134 ms

arrows.woff

arrows.woff

197 ms

rnr-new-banner.png

rnr-new-banner.png

1182 ms

gifts-and-merch-catalogue-new.png

gifts-and-merch-catalogue-new.png

591 ms

corporate-and-team-apparel-catalogue-new.png

corporate-and-team-apparel-catalogue-new.png

984 ms

ppe-new-catalogue.png

ppe-new-catalogue.png

985 ms

loading.gif

loading.gif

315 ms

favicon.png

favicon.png

373 ms

all.js

all.js

7 ms

Accessibility Review

recogniseandreward.co.nz accessibility score

82

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

recogniseandreward.co.nz best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

recogniseandreward.co.nz SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Recogniseandreward.co.nz 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 Recogniseandreward.co.nz 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.

Social Sharing Optimization

recogniseandreward.co.nz

Open Graph description is not detected on the main page of Recogniseandreward. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: