Tools & Wizards About Us
invoice.fans screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

invoice.fans

Invoice.fans welcome! Everything about the e-invoice. - Invoice.fans

Page Load Speed

4.3 sec in total

First Response

243 ms

Resources Loaded

4 sec

Page Rendered

82 ms

invoice.fans screenshot

About Website

Click here to check amazing Invoice content. Otherwise, check out these important facts you probably never knew about invoice.fans

Current information on e-invoice formats like the EN16931 and others in English, German and French. Invoice.fans is an open platform to..

Visit invoice.fans

Key Findings

We analyzed Invoice.fans page load time and found that the first response time was 243 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

invoice.fans performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.142

78/100

15%

TTI (Time to Interactive)

Value4.2 s

85/100

10%

Network Requests Diagram

invoice.fans

243 ms

1083 ms

js

67 ms

tribe-events-pro-mini-calendar-block.min.css

209 ms

style.min.css

418 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 96% of them (70 requests) were addressed to the original Invoice.fans, 3% (2 requests) were made to Ajax.googleapis.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Invoice.fans.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.7 kB (28%)

Content Size

439.1 kB

After Optimization

316.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Invoice.fans main page is 439.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. CSS take 149.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 75.2 kB

  • Original 98.9 kB
  • After minification 97.5 kB
  • After compression 23.7 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 75.2 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 45.3 kB
  • After minification 45.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. Invoice images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 20.0 kB

  • Original 145.3 kB
  • After minification 144.8 kB
  • After compression 125.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 20.0 kB or 14% of the original size.

CSS Optimization

-18%

Potential reduce by 27.5 kB

  • Original 149.6 kB
  • After minification 149.2 kB
  • After compression 122.1 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. Invoice.fans needs all CSS files to be minified and compressed as it can save up to 27.5 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (93%)

Requests Now

59

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

invoice.fans

invoice.fans

243 ms

1083 ms

js

js

67 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

209 ms

style.min.css

style.min.css

418 ms

styles.css

styles.css

323 ms

jquery-ui.min.css

jquery-ui.min.css

25 ms

jquery-ui-timepicker-addon.min.css

jquery-ui-timepicker-addon.min.css

321 ms

wpa.css

wpa.css

323 ms

style.css

style.css

459 ms

style.css

style.css

327 ms

v4-shims.min.css

v4-shims.min.css

436 ms

all.min.css

all.min.css

479 ms

solid.min.css

solid.min.css

437 ms

tablepress-combined.min.css

tablepress-combined.min.css

444 ms

button-styles.css

button-styles.css

524 ms

frontend-gtag.min.js

frontend-gtag.min.js

554 ms

jquery.min.js

jquery.min.js

668 ms

jquery-migrate.min.js

jquery-migrate.min.js

568 ms

widgets-events-common-skeleton.min.css

widgets-events-common-skeleton.min.css

490 ms

widgets-events-common-full.min.css

widgets-events-common-full.min.css

502 ms

variables-skeleton.min.css

variables-skeleton.min.css

560 ms

variables-full.min.css

variables-full.min.css

580 ms

common-skeleton.min.css

common-skeleton.min.css

600 ms

common-full.min.css

common-full.min.css

614 ms

widget-events-list-skeleton.min.css

widget-events-list-skeleton.min.css

618 ms

widget-events-list-full.min.css

widget-events-list-full.min.css

670 ms

widget-events-list-skeleton.min.css

widget-events-list-skeleton.min.css

687 ms

widget-events-list-full.min.css

widget-events-list-full.min.css

693 ms

hooks.min.js

hooks.min.js

712 ms

i18n.min.js

i18n.min.js

730 ms

index.js

index.js

728 ms

index.js

index.js

780 ms

core.min.js

core.min.js

803 ms

datepicker.min.js

datepicker.min.js

816 ms

datepicker-en-GB.min.js

datepicker-en-GB.min.js

6 ms

jquery-ui-timepicker-addon.min.js

jquery-ui-timepicker-addon.min.js

850 ms

jquery-ui-timepicker-en-GB.js

jquery-ui-timepicker-en-GB.js

834 ms

mouse.min.js

mouse.min.js

841 ms

slider.min.js

slider.min.js

900 ms

controlgroup.min.js

controlgroup.min.js

909 ms

checkboxradio.min.js

checkboxradio.min.js

804 ms

button.min.js

button.min.js

708 ms

jquery-ui-sliderAccess.js

jquery-ui-sliderAccess.js

720 ms

wpa.js

wpa.js

727 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

780 ms

navigation.min.js

navigation.min.js

685 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

679 ms

skip-link-focus-fix.min.js

skip-link-focus-fix.min.js

699 ms

colormag-custom.min.js

colormag-custom.min.js

710 ms

tribe-common.min.js

tribe-common.min.js

703 ms

query-string.min.js

query-string.min.js

760 ms

dashicons.min.css

dashicons.min.css

772 ms

font-awesome.min.css

font-awesome.min.css

688 ms

underscore-before.js

underscore-before.js

678 ms

underscore.min.js

underscore.min.js

701 ms

underscore-after.js

underscore-after.js

693 ms

manager.min.js

manager.min.js

741 ms

breakpoints.min.js

breakpoints.min.js

720 ms

GEFEG_Passion-for-Standards_RGB400x100.jpg

GEFEG_Passion-for-Standards_RGB400x100.jpg

115 ms

hintergrund_neutral.png

hintergrund_neutral.png

185 ms

OpenSans-VariableFont.woff

OpenSans-VariableFont.woff

246 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

305 ms

OpenSans-Medium.woff

OpenSans-Medium.woff

238 ms

OpenSans-Light.woff

OpenSans-Light.woff

329 ms

OpenSans-SemiBold.woff

OpenSans-SemiBold.woff

333 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

411 ms

OpenSans-ExtraBold.woff

OpenSans-ExtraBold.woff

399 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

380 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

433 ms

fa-regular-400.ttf

fa-regular-400.ttf

568 ms

fa-brands-400.ttf

fa-brands-400.ttf

611 ms

fa-solid-900.ttf

fa-solid-900.ttf

709 ms

Accessibility Review

invoice.fans accessibility score

80

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

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

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.

Best Practices

invoice.fans 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

Low

Detected JavaScript libraries

SEO Factors

invoice.fans SEO score

100

Search Engine Optimization Advices

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 Invoice.fans 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 Invoice.fans 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

invoice.fans

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