Access efitness.pl. eFitness - dopracowane rozwiązanie do zarządzania obiektem fitness

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value3,650 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.107

88/100

15%

TTI (Time to Interactive)

Value28.8 s

0/100

10%

efitness.pl

333 ms

efitness.pl

698 ms

gtm.js

151 ms

m121zky5vz

149 ms

lazyload.min.js

49 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 36% of them (26 requests) were addressed to the original Efitness.pl, 19% (14 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (698 ms) belongs to the original domain Efitness.pl.

Content Size

4.1 MB

After Optimization

3.3 MB

In fact, the total size of Efitness.pl main page is 4.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 32.4 kB

Original 41.6 kB
After minification 31.6 kB
After compression 9.2 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.9 kB, which is 24% 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 32.4 kB or 78% of the original size.

Image Optimization

-10%

Potential reduce by 293.9 kB

Original 3.0 MB
After minification 2.7 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. EFitness images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 423.2 kB

Original 909.9 kB
After minification 909.9 kB
After compression 486.7 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 423.2 kB or 47% of the original size.

CSS Optimization

-0%

Potential reduce by 536 B

Original 160.3 kB
After minification 160.3 kB
After compression 159.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. Efitness.pl has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EFitness. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 11 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 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

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

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

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Document doesn't have a valid hreflang

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

PL
Language Claimed

PL
Encoding

UTF-8

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

efitness.pl

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

Report Summary

Performance

Accessibility

Best Practices

SEO

eFitness - dopracowane rozwiązanie do zarządzania obiektem fitness

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

efitness.pl

efitness.pl

gtm.js

m121zky5vz

lazyload.min.js

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

efitness.pl

efitness.pl

gtm.js

m121zky5vz

lazyload.min.js

all.min.css

uc.js

sbi-styles.min.css

styles.css

styles.min.css

css

css2

css2

owl.carousel.css

embed.php

jquery.min.js

scripts.js

site_tracking.js

api.js

scripts.js

owl.carousel.min.js

wp-embed.min.js

api.js

clarity.js

c.js

logo-white.svg

ncwPePCzK-o

logo-color.svg

logo-dark.svg

logo-sniadania.svg

form1.png

modal-icon-ok.png

obiekty-fitness.png

obiekty-fitness2.png

clubNetwork.png

efitnessApp.png

eFitnessApp3.png

logo-visa-black.png

EA_PRIDE_LOGO_FC-SLOGAN.png

certificate.png

diffuser.js

recaptcha__en.js

tracking.js