Access mango.pl. Mango.pl

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value33.5 s

0/100

10%

TBT (Total Blocking Time)

Value76,710 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.385

0/100

15%

TTI (Time to Interactive)

Value93.6 s

0/100

10%

mango.pl

397 ms

www.mango.pl

2732 ms

765 ms

1977 ms

1214 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 8% of them (10 requests) were addressed to the original Mango.pl, 51% (66 requests) were made to Static.mango.pl and 6% (8 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (19.1 sec) relates to the external source Static.mango.pl.

Content Size

3.4 MB

After Optimization

2.5 MB

In fact, the total size of Mango.pl main page is 3.4 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 192.9 kB

Original 228.9 kB
After minification 228.7 kB
After compression 36.0 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 192.9 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 96.4 kB

Original 2.2 MB
After minification 2.1 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. Mango images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 541.4 kB

Original 847.8 kB
After minification 843.4 kB
After compression 306.3 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 541.4 kB or 64% of the original size.

CSS Optimization

-81%

Potential reduce by 142.7 kB

Original 175.2 kB
After minification 131.7 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. Mango.pl needs all CSS files to be minified and compressed as it can save up to 142.7 kB or 81% of the original size.

Requests Now

121

After Optimization

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

button, link, and menuitem elements do not have accessible names.

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

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

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

Areas of Improvement

High

Does not use HTTPS

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

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

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