Tools & Wizards About Us
affinityteam.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

affinityteam.com

Payroll Services To Transform Your Business | Affinity

Page Load Speed

6.3 sec in total

First Response

408 ms

Resources Loaded

5.4 sec

Page Rendered

506 ms

affinityteam.com screenshot

About Website

Welcome to affinityteam.com homepage info - get ready to check Affinity Team best content for New Zealand right away, or after learning these important things about affinityteam.com

We provide cost effective, efficient payroll services across Australia and New Zealand. Get your payroll sorted with us and we'll help your payroll pain go away.

Visit affinityteam.com

Key Findings

We analyzed Affinityteam.com page load time and found that the first response time was 408 ms and then it took 5.9 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

affinityteam.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value17.2 s

0/100

10%

TBT (Total Blocking Time)

Value6,740 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

affinityteam.com

408 ms

affinityteam.com

1213 ms

gtm.js

75 ms

style.css

395 ms

font-awesome-legacy.min.css

596 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 76% of them (68 requests) were addressed to the original Affinityteam.com, 4% (4 requests) were made to Googletagmanager.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Affinityteam.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 548.4 kB (52%)

Content Size

1.0 MB

After Optimization

499.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Affinityteam.com main page is 1.0 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. 70% of websites need less resources to load. HTML takes 525.3 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 470.9 kB

  • Original 525.3 kB
  • After minification 373.7 kB
  • After compression 54.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. This page needs HTML code to be minified as it can gain 151.6 kB, which is 29% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 470.9 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 244 B

  • Original 55.4 kB
  • After minification 55.2 kB

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. Affinity Team images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 58.0 kB

  • Original 343.9 kB
  • After minification 343.9 kB
  • After compression 285.9 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 58.0 kB or 17% of the original size.

CSS Optimization

-16%

Potential reduce by 19.2 kB

  • Original 123.6 kB
  • After minification 123.4 kB
  • After compression 104.4 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. Affinityteam.com needs all CSS files to be minified and compressed as it can save up to 19.2 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (65%)

Requests Now

82

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

affinityteam.com

affinityteam.com

408 ms

affinityteam.com

affinityteam.com

1213 ms

gtm.js

gtm.js

75 ms

style.css

style.css

395 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

596 ms

grid-system.css

grid-system.css

592 ms

style.css

style.css

797 ms

header-secondary-nav.css

header-secondary-nav.css

602 ms

element-post-grid.css

element-post-grid.css

599 ms

element-clients.css

element-clients.css

603 ms

caroufredsel.css

caroufredsel.css

795 ms

responsive.css

responsive.css

791 ms

flickity.css

flickity.css

810 ms

select2.css

select2.css

809 ms

skin-original.css

skin-original.css

813 ms

menu-dynamic.css

menu-dynamic.css

982 ms

js_composer.min.css

js_composer.min.css

979 ms

style.css

style.css

982 ms

css

css

26 ms

jquery.min.js

jquery.min.js

1182 ms

jquery-migrate.min.js

jquery-migrate.min.js

990 ms

main.js

main.js

990 ms

js

js

89 ms

analytics.js

analytics.js

33 ms

hotjar-2611647.js

hotjar-2611647.js

104 ms

insight.min.js

insight.min.js

48 ms

roundtrip.js

roundtrip.js

40 ms

collect

collect

33 ms

insight_tag_errors.gif

insight_tag_errors.gif

109 ms

insight_tag_errors.gif

insight_tag_errors.gif

175 ms

front_style.css

front_style.css

990 ms

magnific.css

magnific.css

990 ms

core.css

core.css

992 ms

fullscreen-legacy.css

fullscreen-legacy.css

1254 ms

page-scroll-to-id.min.js

page-scroll-to-id.min.js

1255 ms

salient-social.js

salient-social.js

1387 ms

jquery.easing.js

jquery.easing.js

1387 ms

jquery.mousewheel.js

jquery.mousewheel.js

1387 ms

priority.js

priority.js

1387 ms

transit.js

transit.js

1387 ms

waypoints.js

waypoints.js

1386 ms

imagesLoaded.min.js

imagesLoaded.min.js

1519 ms

hoverintent.js

hoverintent.js

1517 ms

magnific.js

magnific.js

1517 ms

touchswipe.min.js

touchswipe.min.js

1519 ms

caroufredsel.min.js

caroufredsel.min.js

1703 ms

anime.js

anime.js

1522 ms

collect

collect

30 ms

flickity.min.js

flickity.min.js

1899 ms

modules.a4fd7e5489291affcf56.js

modules.a4fd7e5489291affcf56.js

17 ms

__

__

21 ms

superfish.js

superfish.js

1522 ms

init.js

init.js

1709 ms

select2.min.js

select2.min.js

1505 ms

custom.js

custom.js

1312 ms

analyticsjs.js

analyticsjs.js

1521 ms

js_composer_front.min.js

js_composer_front.min.js

1501 ms

js

js

251 ms

js

js

252 ms

init.js

init.js

377 ms

img-logo.png

img-logo.png

896 ms

img-logo-white.png

img-logo-white.png

1142 ms

track.js

track.js

163 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

132 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

179 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

180 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

1114 ms

api.min.js

api.min.js

205 ms

img-affinity-icon-qualified.svg

img-affinity-icon-qualified.svg

231 ms

img-affinity-icon-efficient.svg

img-affinity-icon-efficient.svg

233 ms

img-affinity-icon-compliant.svg

img-affinity-icon-compliant.svg

232 ms

img-affinity-icon-integrated.svg

img-affinity-icon-integrated.svg

229 ms

heritage_life_care.png

heritage_life_care.png

229 ms

tasman_district_council.png

tasman_district_council.png

368 ms

heinz.png

heinz.png

403 ms

hilton.png

hilton.png

404 ms

hoyts.png

hoyts.png

400 ms

volkswagen-finance.png

volkswagen-finance.png

399 ms

new_plymouth.png

new_plymouth.png

401 ms

panasonic.png

panasonic.png

567 ms

slater_and_gordon.png

slater_and_gordon.png

599 ms

smiths.png

smiths.png

598 ms

swatch_group.png

swatch_group.png

602 ms

vector_limited.png

vector_limited.png

601 ms

img-affinity-icon-technology.svg

img-affinity-icon-technology.svg

602 ms

img-affinity-icon-our-applications.svg

img-affinity-icon-our-applications.svg

763 ms

img-affinity-icon-user-experience.svg

img-affinity-icon-user-experience.svg

797 ms

img-affinity-banner-home.jpg

img-affinity-banner-home.jpg

992 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1156 ms

Accessibility Review

affinityteam.com accessibility score

74

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

affinityteam.com 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

affinityteam.com SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Affinityteam.com 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 Affinityteam.com 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

affinityteam.com

Open Graph data is detected on the main page of Affinity Team. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: