Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

weehoo.pl

Przyczepka rowerowa Weehoo - jednośladowa, aktywizująca, z pedałami

Page Load Speed

3.8 sec in total

First Response

473 ms

Resources Loaded

3.1 sec

Page Rendered

228 ms

weehoo.pl screenshot

About Website

Click here to check amazing Weehoo content. Otherwise, check out these important facts you probably never knew about weehoo.pl

Najbardziej aktywizująca przyczepka rowerowa. Weehoo oferuje jednośladowe przyczepki rowerowe z niezależnymi pedałami. Przeżyjcie przygodę razem.

Visit weehoo.pl

Key Findings

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

Performance Metrics

weehoo.pl performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

weehoo.pl

473 ms

jquery-core.min.js

247 ms

styl.css

239 ms

coin-slider.min.js

240 ms

coin-slider-styles.css

240 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 36% of them (27 requests) were addressed to the original Weehoo.pl, 48% (36 requests) were made to Static.xx.fbcdn.net and 7% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (957 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 220.6 kB (23%)

Content Size

949.7 kB

After Optimization

729.1 kB

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

HTML Optimization

-71%

Potential reduce by 9.1 kB

  • Original 12.8 kB
  • After minification 12.6 kB
  • After compression 3.7 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 9.1 kB or 71% of the original size.

Image Optimization

-18%

Potential reduce by 144.2 kB

  • Original 821.1 kB
  • After minification 676.9 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. Obviously, Weehoo needs image optimization as it can save up to 144.2 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-55%

Potential reduce by 57.8 kB

  • Original 104.2 kB
  • After minification 103.8 kB
  • After compression 46.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 57.8 kB or 55% of the original size.

CSS Optimization

-82%

Potential reduce by 9.6 kB

  • Original 11.7 kB
  • After minification 10.7 kB
  • After compression 2.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. Weehoo.pl needs all CSS files to be minified and compressed as it can save up to 9.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (53%)

Requests Now

74

After Optimization

35

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

Accessibility Review

weehoo.pl accessibility score

78

Accessibility Issues

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.

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

High

Links do not have a discernible name

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

weehoo.pl SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Weehoo.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 Weehoo.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 Weehoo. 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: