Tools & Wizards About Us
centricom.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

centricom.com

POLi Online Debit Payments - New Zealand

Page Load Speed

5.5 sec in total

First Response

533 ms

Resources Loaded

4.7 sec

Page Rendered

219 ms

centricom.com screenshot

About Website

Click here to check amazing Centricom content. Otherwise, check out these important facts you probably never knew about centricom.com

POLi allows consumers to make an online payment for goods and services or pay a bill online using the security and convenience of Internet Banking. Register today.

Visit centricom.com

Key Findings

We analyzed Centricom.com page load time and found that the first response time was 533 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster. This domain responded with an error, which can significantly jeopardize Centricom.com rating and web reputation

Performance Metrics

centricom.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value1,880 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

centricom.com

533 ms

www.polipayments.com

1071 ms

css

479 ms

responsive

691 ms

modernizr

693 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Centricom.com, 65% (40 requests) were made to Polipayments.com and 24% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Polipayments.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.0 kB (7%)

Content Size

316.1 kB

After Optimization

293.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Centricom.com main page is 316.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 275.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 15.1 kB

  • Original 19.5 kB
  • After minification 15.0 kB
  • After compression 4.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 4.5 kB, which is 23% 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 15.1 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 7.8 kB

  • Original 275.6 kB
  • After minification 267.8 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. Centricom images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 12 (29%)

Requests Now

41

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

centricom.com

centricom.com

533 ms

www.polipayments.com

www.polipayments.com

1071 ms

css

css

479 ms

responsive

responsive

691 ms

modernizr

modernizr

693 ms

css

css

60 ms

css

css

72 ms

jquery

jquery

1147 ms

Sticky.js

Sticky.js

810 ms

respond.js

respond.js

810 ms

analytics.js

analytics.js

116 ms

Logo.png

Logo.png

694 ms

padlock.png

padlock.png

237 ms

orange_chevron.png

orange_chevron.png

231 ms

home.png

home.png

314 ms

bluebutton.png

bluebutton.png

313 ms

xero.png

xero.png

461 ms

dots_overlay.png

dots_overlay.png

469 ms

poster.jpg

poster.jpg

1452 ms

buy_button.png

buy_button.png

770 ms

sell_button.png

sell_button.png

645 ms

qantas.png

qantas.png

690 ms

worldremit.png

worldremit.png

700 ms

jetstar.png

jetstar.png

880 ms

virgin.png

virgin.png

919 ms

williamhill.png

williamhill.png

921 ms

sportsbet.png

sportsbet.png

931 ms

etihad.jpg

etihad.jpg

999 ms

airasia.png

airasia.png

1108 ms

crownbet.png

crownbet.png

1149 ms

orange.png

orange.png

1152 ms

quote_orange.png

quote_orange.png

1162 ms

blue_chevron.png

blue_chevron.png

1228 ms

blue.png

blue.png

1337 ms

fb.png

fb.png

1378 ms

grey.png

grey.png

1383 ms

news.png

news.png

1393 ms

twitter.png

twitter.png

1456 ms

white_chevron.png

white_chevron.png

1565 ms

facebook.png

facebook.png

1605 ms

twitter.png

twitter.png

1613 ms

google.png

google.png

1625 ms

youtube.png

youtube.png

1675 ms

mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf

mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf

64 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

63 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

63 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

62 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

61 ms

Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf

Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf

62 ms

APLetter_Web-Medium.otf

APLetter_Web-Medium.otf

2294 ms

7m8l7TlFO-S3VkhHuR0at50EAVxt0G0biEntp43Qt6E.ttf

7m8l7TlFO-S3VkhHuR0at50EAVxt0G0biEntp43Qt6E.ttf

106 ms

12mE4jfMSBTmg-81EiS-YS3USBnSvpkopQaUR-2r7iU.ttf

12mE4jfMSBTmg-81EiS-YS3USBnSvpkopQaUR-2r7iU.ttf

104 ms

W4wDsBUluyw0tK3tykhXEfesZW2xOQ-xsNqO47m55DA.ttf

W4wDsBUluyw0tK3tykhXEfesZW2xOQ-xsNqO47m55DA.ttf

110 ms

OLffGBTaF0XFOW1gnuHF0Z0EAVxt0G0biEntp43Qt6E.ttf

OLffGBTaF0XFOW1gnuHF0Z0EAVxt0G0biEntp43Qt6E.ttf

104 ms

t6Nd4cfPRhZP44Q5QAjcC50EAVxt0G0biEntp43Qt6E.ttf

t6Nd4cfPRhZP44Q5QAjcC50EAVxt0G0biEntp43Qt6E.ttf

96 ms

bmC0pGMXrhphrZJmniIZpZ0EAVxt0G0biEntp43Qt6E.ttf

bmC0pGMXrhphrZJmniIZpZ0EAVxt0G0biEntp43Qt6E.ttf

95 ms

b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf

b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf

102 ms

Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf

Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf

102 ms

b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf

b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf

101 ms

collect

collect

67 ms

collect

collect

54 ms

ga-audiences

ga-audiences

40 ms

Accessibility Review

centricom.com accessibility score

67

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

centricom.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Missing source maps for large first-party JavaScript

SEO Factors

centricom.com SEO score

85

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

Links do not have descriptive text

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 Centricom.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 Centricom.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

centricom.com

Open Graph description is not detected on the main page of Centricom. 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: