Tools & Wizards About Us
2sides.pl screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

2sides.pl

2Sides - e-commerce, strony, sklepy internetowe

Page Load Speed

6.4 sec in total

First Response

1.1 sec

Resources Loaded

4.8 sec

Page Rendered

405 ms

2sides.pl screenshot

About Website

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

Soon...

Visit 2sides.pl

Key Findings

We analyzed 2sides.pl page load time and found that the first response time was 1.1 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

2sides.pl performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.3 s

100/100

10%

Network Requests Diagram

2sides.pl

1102 ms

css

63 ms

css

40 ms

css

52 ms

style.css

1007 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 78% of them (43 requests) were addressed to the original 2sides.pl, 13% (7 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain 2sides.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 927.4 kB (44%)

Content Size

2.1 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 39.0 kB

  • Original 50.4 kB
  • After minification 46.5 kB
  • After compression 11.4 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 39.0 kB or 77% of the original size.

Image Optimization

-9%

Potential reduce by 94.8 kB

  • Original 1.1 MB
  • After minification 1.0 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. 2Sides images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 370.7 kB

  • Original 502.3 kB
  • After minification 448.9 kB
  • After compression 131.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 370.7 kB or 74% of the original size.

CSS Optimization

-89%

Potential reduce by 422.9 kB

  • Original 477.1 kB
  • After minification 423.9 kB
  • After compression 54.2 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. 2sides.pl needs all CSS files to be minified and compressed as it can save up to 422.9 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (50%)

Requests Now

46

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

2sides.pl

2sides.pl

1102 ms

css

css

63 ms

css

css

40 ms

css

css

52 ms

style.css

style.css

1007 ms

shortcodes.css

shortcodes.css

344 ms

shortcodes_responsive.css

shortcodes_responsive.css

246 ms

magnific_popup.css

magnific_popup.css

243 ms

jquery.js

jquery.js

611 ms

jquery-migrate.min.js

jquery-migrate.min.js

334 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

516 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

499 ms

wp-mediaelement.css

wp-mediaelement.css

572 ms

frontend-builder-global-functions.js

frontend-builder-global-functions.js

559 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

732 ms

custom.js

custom.js

1008 ms

smoothscroll.js

smoothscroll.js

774 ms

jquery.fitvids.js

jquery.fitvids.js

832 ms

waypoints.min.js

waypoints.min.js

840 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

1074 ms

frontend-builder-scripts.js

frontend-builder-scripts.js

1338 ms

wp-embed.min.js

wp-embed.min.js

1075 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1430 ms

wp-mediaelement.js

wp-mediaelement.js

1367 ms

jquery.easypiechart.js

jquery.easypiechart.js

1373 ms

logo.png

logo.png

640 ms

preloader.gif

preloader.gif

641 ms

zarowka.jpg

zarowka.jpg

659 ms

linia.jpg

linia.jpg

763 ms

olow.jpg

olow.jpg

746 ms

cog.jpg

cog.jpg

739 ms

tlo_vevey.jpg

tlo_vevey.jpg

1113 ms

vevey.png

vevey.png

1194 ms

kim_main.jpg

kim_main.jpg

888 ms

tlo_weyzk.jpg

tlo_weyzk.jpg

1223 ms

wezyk.png

wezyk.png

1349 ms

dk2.jpg

dk2.jpg

1431 ms

image12.jpg

image12.jpg

1726 ms

mm-na-strtone.jpg

mm-na-strtone.jpg

2255 ms

tlo_wat.jpg

tlo_wat.jpg

1685 ms

WAT1.png

WAT1.png

1823 ms

onas.jpg

onas.jpg

1772 ms

my.jpg

my.jpg

1739 ms

tlo_wonder.jpg

tlo_wonder.jpg

2268 ms

Wonder_room.png

Wonder_room.png

2165 ms

analytics.js

analytics.js

6 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

26 ms

BTu4SsVveqk58cdYjlaM9g.ttf

BTu4SsVveqk58cdYjlaM9g.ttf

50 ms

zJY4gsxBiSo5L7tNutxFNg.ttf

zJY4gsxBiSo5L7tNutxFNg.ttf

27 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

49 ms

4GwpJM7qx9X5Obd9KsnKxQ.ttf

4GwpJM7qx9X5Obd9KsnKxQ.ttf

50 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

27 ms

4cKlrioa77J2iqTqBgkRWg.ttf

4cKlrioa77J2iqTqBgkRWg.ttf

49 ms

ETmodules_v2_4.ttf

ETmodules_v2_4.ttf

2703 ms

collect

collect

27 ms

Accessibility Review

2sides.pl accessibility score

100

Accessibility Issues

Best Practices

2sides.pl best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

2sides.pl SEO score

100

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    PL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2sides.pl can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Polish. Our system also found out that 2sides.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

2sides.pl

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