Tools & Wizards About Us
swiffpay.com screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 35

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

swiffpay.com

Swiffpay - Secure credit card payments on the move

Page Load Speed

1.9 sec in total

First Response

36 ms

Resources Loaded

1.6 sec

Page Rendered

178 ms

swiffpay.com screenshot

About Website

Welcome to swiffpay.com homepage info - get ready to check Swiffpay best content right away, or after learning these important things about swiffpay.com

SwiffPay is the world's first white-label mobile payment platform that offers a patented, bank-standard security.

Visit swiffpay.com

Key Findings

We analyzed Swiffpay.com page load time and found that the first response time was 36 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

swiffpay.com performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.245

51/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

swiffpay.com

36 ms

swiffpay.com

259 ms

www.swiffpay.com

58 ms

www.swiffpay.com

242 ms

jquery.min.js

183 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that all of those requests were addressed to Swiffpay.com and no external sources were called. The less responsive or slowest element that took the longest time to load (746 ms) belongs to the original domain Swiffpay.com.

Page Optimization Overview & Recommendations

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

Content Size

949.8 kB

After Optimization

882.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Swiffpay.com main page is 949.8 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. 15% of websites need less resources to load. Images take 867.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 25.9 kB

  • Original 32.4 kB
  • After minification 23.1 kB
  • After compression 6.5 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 9.2 kB, which is 28% 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 25.9 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 36.9 kB

  • Original 867.3 kB
  • After minification 830.3 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. Swiffpay images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 3.9 kB

  • Original 45.8 kB
  • After minification 45.8 kB
  • After compression 41.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.

CSS Optimization

-18%

Potential reduce by 796 B

  • Original 4.4 kB
  • After minification 4.4 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. Swiffpay.com needs all CSS files to be minified and compressed as it can save up to 796 B or 18% of the original size.

Requests Breakdown

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

Requests Now

35

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Swiffpay. 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 as a result speed up the page load time.

Network Requests Diagram

swiffpay.com

swiffpay.com

36 ms

swiffpay.com

swiffpay.com

259 ms

www.swiffpay.com

www.swiffpay.com

58 ms

www.swiffpay.com

www.swiffpay.com

242 ms

jquery.min.js

jquery.min.js

183 ms

jquery.colorbox.js

jquery.colorbox.js

225 ms

swiff_v3.js

swiff_v3.js

245 ms

fade-plugin.js

fade-plugin.js

220 ms

styles.css

styles.css

238 ms

bgbody.png

bgbody.png

348 ms

bgtop_bar.png

bgtop_bar.png

279 ms

twitter_icon.png

twitter_icon.png

111 ms

fb_icon.png

fb_icon.png

103 ms

bgrepeat.png

bgrepeat.png

112 ms

bgheader.jpg

bgheader.jpg

252 ms

actual_iphone.png

actual_iphone.png

473 ms

screenshot1.jpg

screenshot1.jpg

312 ms

screenshot2.jpg

screenshot2.jpg

323 ms

screenshot3.jpg

screenshot3.jpg

441 ms

tryitnow_button.png

tryitnow_button.png

378 ms

swifflogo_big.png

swifflogo_big.png

515 ms

swiff_tagline_v1.png

swiff_tagline_v1.png

440 ms

register_button.png

register_button.png

445 ms

enter_button.png

enter_button.png

478 ms

appstore_button.png

appstore_button.png

551 ms

sep.png

sep.png

543 ms

androidmarket_button.png

androidmarket_button.png

542 ms

moveimage.png

moveimage.png

575 ms

news_icon_list.png

news_icon_list.png

584 ms

bsecureLogo.png

bsecureLogo.png

627 ms

octopusLogo.png

octopusLogo.png

642 ms

lufraLogo.jpg

lufraLogo.jpg

645 ms

zimerickLogo.png

zimerickLogo.png

660 ms

illigoLogo.png

illigoLogo.png

676 ms

samsungLogo.png

samsungLogo.png

687 ms

bgfooter.png

bgfooter.png

746 ms

overlay.png

overlay.png

691 ms

border.png

border.png

712 ms

controls.png

controls.png

728 ms

Rockwell%20Std%20Light.ttf

Rockwell%20Std%20Light.ttf

732 ms

Accessibility Review

swiffpay.com accessibility score

35

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

swiffpay.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

swiffpay.com SEO score

71

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

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

swiffpay.com

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