Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

brotex.pl

BROTEX - producent swetrów, swetry. | Dziewiarstwo - ul.Gałczyńskiego 4, 42-300 Myszków

Page Load Speed

3.9 sec in total

First Response

360 ms

Resources Loaded

2.9 sec

Page Rendered

588 ms

About Website

Visit brotex.pl now to see the best up-to-date BROTEX content and also check out these interesting facts you probably never knew about brotex.pl

Oferta producenta swetrów BROTEX: swetry damskie i męskie, dziewiarstwo. ul.Gałczyńskiego 4, 42-300 Myszków.

Visit brotex.pl

Key Findings

We analyzed Brotex.pl page load time and found that the first response time was 360 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

brotex.pl performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.211

59/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

brotex.pl

360 ms

www.brotex.pl

603 ms

font-awesome.min.css

55 ms

css

41 ms

css2

57 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 76% of them (50 requests) were addressed to the original Brotex.pl, 8% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Brotex.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (15%)

Content Size

6.8 MB

After Optimization

5.8 MB

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

HTML Optimization

-84%

Potential reduce by 31.0 kB

  • Original 36.9 kB
  • After minification 27.5 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 9.4 kB, which is 25% 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 31.0 kB or 84% of the original size.

Image Optimization

-15%

Potential reduce by 1.0 MB

  • Original 6.7 MB
  • After minification 5.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. Obviously, BROTEX needs image optimization as it can save up to 1.0 MB 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

-7%

Potential reduce by 4.3 kB

  • Original 57.7 kB
  • After minification 57.7 kB
  • After compression 53.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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 1.8 kB

  • Original 30.2 kB
  • After minification 30.2 kB
  • After compression 28.4 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. Brotex.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (29%)

Requests Now

58

After Optimization

41

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

Accessibility Review

brotex.pl accessibility score

82

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 input fields do not have accessible names

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

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

brotex.pl best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

brotex.pl SEO score

71

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    PL

  • Language Claimed

    PL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brotex.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 Brotex.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 BROTEX. 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: