Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

payex.se

PayEx - Fakturahantering och finansiering för företag

Page Load Speed

3 sec in total

First Response

486 ms

Resources Loaded

2.1 sec

Page Rendered

401 ms

payex.se screenshot

About Website

Visit payex.se now to see the best up-to-date Pay Ex content for Sweden and also check out these interesting facts you probably never knew about payex.se

Flexibla lösningar för komplexa affärer. PayEx tar hand om fakturering, finansiering och inkasso på ett sätt som är anpassat efter just ditt företag.

Visit payex.se

Key Findings

We analyzed Payex.se page load time and found that the first response time was 486 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

payex.se performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

74/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value9,670 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

payex.se

486 ms

bootstrap.min.css

409 ms

bootstrap.css

245 ms

slidebars.css

241 ms

flickity.css

242 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 67% of them (33 requests) were addressed to the original Payex.se, 16% (8 requests) were made to and 4% (2 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (982 ms) belongs to the original domain Payex.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 412.2 kB (39%)

Content Size

1.1 MB

After Optimization

648.5 kB

In fact, the total size of Payex.se main page is 1.1 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. 45% of websites need less resources to load. Images take 657.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 25.5 kB

  • Original 33.8 kB
  • After minification 27.0 kB
  • After compression 8.3 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 6.8 kB, which is 20% 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.5 kB or 75% of the original size.

Image Optimization

-15%

Potential reduce by 101.3 kB

  • Original 657.7 kB
  • After minification 556.4 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. Obviously, Pay Ex needs image optimization as it can save up to 101.3 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 128.5 kB

  • Original 179.9 kB
  • After minification 163.4 kB
  • After compression 51.4 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 128.5 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 156.9 kB

  • Original 189.4 kB
  • After minification 174.9 kB
  • After compression 32.5 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. Payex.se needs all CSS files to be minified and compressed as it can save up to 156.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (63%)

Requests Now

40

After Optimization

15

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

Accessibility Review

payex.se 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

High

Links do not have a discernible name

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

payex.se best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

payex.se SEO score

85

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    SV

  • Language Claimed

    SV

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Payex.se can be misinterpreted by Google and other search engines. Our service has detected that Swedish is used on the page, and it matches the claimed language. Our system also found out that Payex.se 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

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