Access feesa.net. KBC Technology and Consulting in Digital Energy & Carbon Emissions Management

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

1/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.8 s

36/100

10%

feesa.net

938 ms

css

25 ms

css

37 ms

prettylinks_shiny.css

299 ms

layerslider.css

384 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 92% of them (89 requests) were addressed to the original Feesa.net, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Feesa.net.

Content Size

8.3 MB

After Optimization

6.3 MB

In fact, the total size of Feesa.net main page is 8.3 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. 65% of websites need less resources to load. Images take 6.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 43.4 kB

Original 53.1 kB
After minification 49.0 kB
After compression 9.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 43.4 kB or 82% of the original size.

Image Optimization

-12%

Potential reduce by 830.8 kB

Original 6.8 MB
After minification 5.9 MB

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, Feesa needs image optimization as it can save up to 830.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 719.4 kB

Original 984.6 kB
After minification 873.6 kB
After compression 265.2 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 719.4 kB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 443.4 kB

Original 523.1 kB
After minification 446.9 kB
After compression 79.7 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. Feesa.net needs all CSS files to be minified and compressed as it can save up to 443.4 kB or 85% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Feesa.net 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 Feesa.net 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 Feesa. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

KBC Technology and Consulting in Digital Energy & Carbon Emissions Management

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

feesa.net

css

css

prettylinks_shiny.css

layerslider.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

{{url}}

Accessibility Review

Accessibility Issues

Best Practices

Areas of Improvement

SEO Factors

Search Engine Optimization Advices

Language and Encoding

Language Detected

Language Claimed

Encoding

Social Sharing Optimization

{{og_title}}