Tools & Wizards About Us
fts.pl screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

fts.pl

Sklep Vans - Wyprzedaż oryginalnych ubrań | Elwix.pl

Page Load Speed

4.7 sec in total

First Response

247 ms

Resources Loaded

3.7 sec

Page Rendered

731 ms

fts.pl screenshot

About Website

Welcome to fts.pl homepage info - get ready to check Fts best content right away, or after learning these important things about fts.pl

Kochamy prostotę i niebanalny design produktów marki Vans. Dlatego nie mogło ich zabraknąć w naszym sklepie. Znajdziesz tu buty damskie i męskie, plecaki, piórniki, a także skarpetki i czapki.

Visit fts.pl

Key Findings

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

Performance Metrics

fts.pl performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value2,180 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.226

55/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

fts.pl

247 ms

vans

1172 ms

gtm.js

58 ms

e481d5b355bdc114d642f1ca1653a213.css

459 ms

js

108 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fts.pl, 87% (69 requests) were made to Elwix.pl and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Elwix.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 449.1 kB (57%)

Content Size

788.2 kB

After Optimization

339.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fts.pl main page is 788.2 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. 65% of websites need less resources to load. HTML takes 497.6 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 445.4 kB

  • Original 497.6 kB
  • After minification 349.9 kB
  • After compression 52.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 147.6 kB, which is 30% 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 445.4 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 46 B

  • Original 16.4 kB
  • After minification 16.4 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. Fts images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.4 kB

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

CSS Optimization

-2%

Potential reduce by 2.3 kB

  • Original 97.7 kB
  • After minification 97.7 kB
  • After compression 95.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. Fts.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (13%)

Requests Now

77

After Optimization

67

  • Images
  • JavaScript
  • CSS

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fts. 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 as a result speed up the page load time.

Network Requests Diagram

fts.pl

fts.pl

247 ms

vans

vans

1172 ms

gtm.js

gtm.js

58 ms

e481d5b355bdc114d642f1ca1653a213.css

e481d5b355bdc114d642f1ca1653a213.css

459 ms

js

js

108 ms

consent.js

consent.js

149 ms

js

js

66 ms

email-decode.min.js

email-decode.min.js

9 ms

a71f652ccfd2946bfa2feed2b1b8fdf2.js

a71f652ccfd2946bfa2feed2b1b8fdf2.js

526 ms

conversion.js

conversion.js

81 ms

banner.no-autoblock.js

banner.no-autoblock.js

5 ms

sprite.defs.svg

sprite.defs.svg

91 ms

sprite.defs.svg

sprite.defs.svg

463 ms

thumb_menu-meskie.webp

thumb_menu-meskie.webp

668 ms

thumb_menu-damskie.webp

thumb_menu-damskie.webp

623 ms

thumb_menu-mlodziez.webp

thumb_menu-mlodziez.webp

103 ms

thumb_menu-nowosci.webp

thumb_menu-nowosci.webp

106 ms

thumb_menu-wyprzedaz.webp

thumb_menu-wyprzedaz.webp

116 ms

sprite.defs.svg

sprite.defs.svg

121 ms

sprite.defs.svg

sprite.defs.svg

134 ms

sprite.defs.svg

sprite.defs.svg

139 ms

large_5.webp

large_5.webp

552 ms

sprite.view.svg

sprite.view.svg

609 ms

sprite.view.svg

sprite.view.svg

668 ms

small_r0kjepAygSTdHNZsmKY4.webp

small_r0kjepAygSTdHNZsmKY4.webp

752 ms

sprite.defs.svg

sprite.defs.svg

564 ms

small_xPyf2D3i5XGb6EuznHlK.webp

small_xPyf2D3i5XGb6EuznHlK.webp

826 ms

small_QsPvhn6B0NAqYz5L8xtg.webp

small_QsPvhn6B0NAqYz5L8xtg.webp

827 ms

small_AXCj5wJkfREcMdGrgzmB.webp

small_AXCj5wJkfREcMdGrgzmB.webp

631 ms

small_MqRxLCQprn3IK9V0wuyi.webp

small_MqRxLCQprn3IK9V0wuyi.webp

666 ms

small_30CMhcSROLVNpEXsek2w.webp

small_30CMhcSROLVNpEXsek2w.webp

681 ms

small_BH0MrauEcK1Xqpg5TlbF.webp

small_BH0MrauEcK1Xqpg5TlbF.webp

896 ms

small_ZL5CdStDcXnilF6IJgz7.webp

small_ZL5CdStDcXnilF6IJgz7.webp

897 ms

small_7FcWq0MCKlSENxVUdkX5.webp

small_7FcWq0MCKlSENxVUdkX5.webp

714 ms

small_DLZjtyVWX5p60AK13UEw.webp

small_DLZjtyVWX5p60AK13UEw.webp

750 ms

small_0zXp6cwqaonExIDuZgCd.webp

small_0zXp6cwqaonExIDuZgCd.webp

951 ms

small_GKToptxg0hmSqfJZY4XP.webp

small_GKToptxg0hmSqfJZY4XP.webp

751 ms

small_MP7fIVZHe1uhEF0OLzUS.webp

small_MP7fIVZHe1uhEF0OLzUS.webp

750 ms

small_WtAv9yPYzKHOC7Fg8rLM.webp

small_WtAv9yPYzKHOC7Fg8rLM.webp

786 ms

small_9Pfi2phwGrH358Dtq7jV.webp

small_9Pfi2phwGrH358Dtq7jV.webp

787 ms

small_yehsGnBa2dXkCr3mA0Fx.webp

small_yehsGnBa2dXkCr3mA0Fx.webp

788 ms

small_FjQGPVkM5v0lXiuZpxng.webp

small_FjQGPVkM5v0lXiuZpxng.webp

788 ms

small_hRNsiP4kDbWmr2E7tTSX.webp

small_hRNsiP4kDbWmr2E7tTSX.webp

825 ms

small_qnizMgjPfepbJ3C2UoQa.webp

small_qnizMgjPfepbJ3C2UoQa.webp

1032 ms

small_w0l3OD2GUbr4QPhxAKYV.webp

small_w0l3OD2GUbr4QPhxAKYV.webp

825 ms

small_VN0A456AY281.webp

small_VN0A456AY281.webp

989 ms

small_gO1Kx7HBmXT0r3ILd9oh.webp

small_gO1Kx7HBmXT0r3ILd9oh.webp

767 ms

small_rzYDlSscTO4oK3Rx1eqG.webp

small_rzYDlSscTO4oK3Rx1eqG.webp

761 ms

small_RLWciq4bCfvIXHrEKlhz.webp

small_RLWciq4bCfvIXHrEKlhz.webp

758 ms

small_T3cgl0JCAwrnGqm4FjHU.webp

small_T3cgl0JCAwrnGqm4FjHU.webp

995 ms

small_VN000XOIY281.webp

small_VN000XOIY281.webp

872 ms

small_steXx0dEpZ4SLYfNhcuV.webp

small_steXx0dEpZ4SLYfNhcuV.webp

973 ms

small_h8B74D5c1tsdH9fOLCSb.webp

small_h8B74D5c1tsdH9fOLCSb.webp

1050 ms

tr.js

tr.js

792 ms

34 ms

small_NxVZOvFp4Ck28lygJrAY.webp

small_NxVZOvFp4Ck28lygJrAY.webp

1016 ms

29 ms

small_srmjEqpcCPxy6NWgLth5.webp

small_srmjEqpcCPxy6NWgLth5.webp

803 ms

small_s67PHMVwZekJhyIDp4Od.webp

small_s67PHMVwZekJhyIDp4Od.webp

751 ms

small_6fbkRYwyXd0HOavCLlEz.webp

small_6fbkRYwyXd0HOavCLlEz.webp

767 ms

small_UyIwSjvPX4aeCYgGmD9O.webp

small_UyIwSjvPX4aeCYgGmD9O.webp

720 ms

small_ufjP3Ur9Hxcd25Bg8Zp6.webp

small_ufjP3Ur9Hxcd25Bg8Zp6.webp

808 ms

small_HoU1pGuZTR0eS9C8Yzrb.webp

small_HoU1pGuZTR0eS9C8Yzrb.webp

804 ms

small_sfJ4jpMxLBqmuy2hNXOG.webp

small_sfJ4jpMxLBqmuy2hNXOG.webp

842 ms

small_wa3rNqu6Sj2TbX4JvKxR.webp

small_wa3rNqu6Sj2TbX4JvKxR.webp

866 ms

small_AKLgWceR0w34J28mdsCF.webp

small_AKLgWceR0w34J28mdsCF.webp

916 ms

small_6YO2osdh4wGpLb9ifJ13.webp

small_6YO2osdh4wGpLb9ifJ13.webp

884 ms

small_iZGDNOPIXM89HJc204W7.webp

small_iZGDNOPIXM89HJc204W7.webp

913 ms

small_JCWkbwvcO3P675mHaXAG.webp

small_JCWkbwvcO3P675mHaXAG.webp

951 ms

small_pqXhyxHT3gEkeVcN8YiR.webp

small_pqXhyxHT3gEkeVcN8YiR.webp

1103 ms

small_xUsWMLYrPQ8cKbwCVZTi.webp

small_xUsWMLYrPQ8cKbwCVZTi.webp

1013 ms

small_UExWo4YAgPG2hZsTlrS8.webp

small_UExWo4YAgPG2hZsTlrS8.webp

1025 ms

small_uD0jKwFObm3AElr75ykW.webp

small_uD0jKwFObm3AElr75ykW.webp

1025 ms

small_DaMfSH0kgvOoKum3PCwX.webp

small_DaMfSH0kgvOoKum3PCwX.webp

1106 ms

small_nu1lQCTxdXzMp8y0keL3.webp

small_nu1lQCTxdXzMp8y0keL3.webp

1145 ms

thumb_newsletter.webp

thumb_newsletter.webp

980 ms

sprite.defs.svg

sprite.defs.svg

979 ms

pfr.jpg

pfr.jpg

1027 ms

jquery.md5.js

jquery.md5.js

628 ms

Accessibility Review

fts.pl accessibility score

87

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

fts.pl best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fts.pl SEO score

83

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

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

fts.pl

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