Tools & Wizards About Us
paymentexpress.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

paymentexpress.com

Payment Express | Home | EFTPOS | Payment Gateway | Online Credit & Debit Card Processing

Page Load Speed

3.3 sec in total

First Response

461 ms

Resources Loaded

2.6 sec

Page Rendered

224 ms

paymentexpress.com screenshot

About Website

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

PCI compliant payment gateway for merchants worldwide accepting credit & debit cards in Retail, Online, Call centre, OPT/UPT & Vending environments.

Visit paymentexpress.com

Key Findings

We analyzed Paymentexpress.com page load time and found that the first response time was 461 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

paymentexpress.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

www.paymentexpress.com

461 ms

GetCSS.aspx

222 ms

ga.js

59 ms

GetCSS.aspx

387 ms

WebResource.axd

393 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 93% of them (38 requests) were addressed to the original Paymentexpress.com, 7% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Paymentexpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 398.7 kB (47%)

Content Size

843.0 kB

After Optimization

444.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Paymentexpress.com main page is 843.0 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. 35% of websites need less resources to load. Javascripts take 467.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 52.7 kB

  • Original 64.5 kB
  • After minification 60.9 kB
  • After compression 11.8 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 52.7 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 13.5 kB

  • Original 288.4 kB
  • After minification 274.9 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. Payment Express images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 313.8 kB

  • Original 467.7 kB
  • After minification 460.0 kB
  • After compression 154.0 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 313.8 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 18.8 kB

  • Original 22.4 kB
  • After minification 18.5 kB
  • After compression 3.6 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. Paymentexpress.com needs all CSS files to be minified and compressed as it can save up to 18.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (49%)

Requests Now

37

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.paymentexpress.com

www.paymentexpress.com

461 ms

GetCSS.aspx

GetCSS.aspx

222 ms

ga.js

ga.js

59 ms

GetCSS.aspx

GetCSS.aspx

387 ms

WebResource.axd

WebResource.axd

393 ms

GetResource.ashx

GetResource.ashx

578 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

595 ms

coin-slider.js

coin-slider.js

395 ms

ScriptResource.axd

ScriptResource.axd

420 ms

ScriptResource.axd

ScriptResource.axd

593 ms

PortalTemplate.aspx

PortalTemplate.aspx

593 ms

jquery_scrollto.js

jquery_scrollto.js

594 ms

__utm.gif

__utm.gif

30 ms

ga.js

ga.js

43 ms

paymentexpress.png

paymentexpress.png

256 ms

Search.png

Search.png

386 ms

twitter.png

twitter.png

388 ms

linkedin.png

linkedin.png

393 ms

learnmore.png

learnmore.png

399 ms

EMV-tile.jpg

EMV-tile.jpg

598 ms

Xero-tile.jpg

Xero-tile.jpg

625 ms

Partners-Tile.jpg

Partners-Tile.jpg

580 ms

Globe_homepage.jpg

Globe_homepage.jpg

772 ms

Unattended.jpg

Unattended.jpg

585 ms

productsicon.png

productsicon.png

594 ms

learnmore2.png

learnmore2.png

773 ms

developersicon.png

developersicon.png

778 ms

supporticon.png

supporticon.png

789 ms

partnersicon.png

partnersicon.png

790 ms

dpsLogo

dpsLogo

822 ms

background.png

background.png

719 ms

footbot.png

footbot.png

719 ms

curvedtop.png

curvedtop.png

720 ms

arrow.png

arrow.png

736 ms

lock.png

lock.png

737 ms

homebot.png

homebot.png

751 ms

homebotbot.png

homebotbot.png

893 ms

232963_0_0.woff

232963_0_0.woff

1085 ms

232963_2_0.woff

232963_2_0.woff

1090 ms

232963_1_0.woff

232963_1_0.woff

1109 ms

globe_usa.png

globe_usa.png

872 ms

Accessibility Review

paymentexpress.com accessibility score

85

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

Image elements do not have [alt] attributes

Best Practices

paymentexpress.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Paymentexpress.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Paymentexpress.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

paymentexpress.com

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