Tools & Wizards About Us
filttr.pl screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

filttr.pl

FILTTR - łatwo zatrudniaj odpowiednich specjalistów IT

Page Load Speed

5.5 sec in total

First Response

316 ms

Resources Loaded

4 sec

Page Rendered

1.2 sec

filttr.pl screenshot

About Website

Welcome to filttr.pl homepage info - get ready to check FILTTR best content for Poland right away, or after learning these important things about filttr.pl

Włącz konkretne propozycje – bez ogłoszeń, bez bełkotu, bez spamu. Tak konkretnie w IT nie mówi nikt! Zobacz naszą unikalną formę oferty opracowaną przez samych specjalistów IT.

Visit filttr.pl

Key Findings

We analyzed Filttr.pl page load time and found that the first response time was 316 ms and then it took 5.2 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

filttr.pl performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.3 s

100/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value4,760 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

filttr.pl

316 ms

230 ms

hotjar-272265.js

301 ms

main.css

271 ms

modernizr.js

504 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 59% of them (36 requests) were addressed to the original Filttr.pl, 11% (7 requests) were made to Youtube.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source In.hotjar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 980.1 kB (64%)

Content Size

1.5 MB

After Optimization

551.0 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 21.0 kB

  • Original 28.3 kB
  • After minification 24.9 kB
  • After compression 7.3 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 3.3 kB, which is 12% 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 21.0 kB or 74% of the original size.

JavaScript Optimization

-55%

Potential reduce by 577.9 kB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 477.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 577.9 kB or 55% of the original size.

CSS Optimization

-85%

Potential reduce by 381.3 kB

  • Original 447.6 kB
  • After minification 424.6 kB
  • After compression 66.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. Filttr.pl needs all CSS files to be minified and compressed as it can save up to 381.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (54%)

Requests Now

50

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

filttr.pl

filttr.pl

316 ms

230 ms

hotjar-272265.js

hotjar-272265.js

301 ms

main.css

main.css

271 ms

modernizr.js

modernizr.js

504 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

209 ms

libs.min.js

libs.min.js

1058 ms

app.min.js

app.min.js

753 ms

angular.min.js

angular.min.js

418 ms

angular-cookies.js

angular-cookies.js

427 ms

angular-ui-router.min.js

angular-ui-router.min.js

434 ms

jwt-decode.min.js

jwt-decode.min.js

357 ms

app.js

app.js

814 ms

utils.js

utils.js

813 ms

ui-bootstrap-0.12.0.min.js

ui-bootstrap-0.12.0.min.js

813 ms

ui-bootstrap-tpls-0.12.0.min.js

ui-bootstrap-tpls-0.12.0.min.js

923 ms

config.js

config.js

932 ms

validatorService.js

validatorService.js

932 ms

authenticationCtrl.js

authenticationCtrl.js

932 ms

authenticationService.js

authenticationService.js

931 ms

cookies.js

cookies.js

1002 ms

cookies.css

cookies.css

1008 ms

modules.b98d976b35a426609eb5.js

modules.b98d976b35a426609eb5.js

556 ms

recorder.js

recorder.js

464 ms

loader.js

loader.js

474 ms

logo-white.svg

logo-white.svg

431 ms

x.png

x.png

647 ms

grafika2.png

grafika2.png

867 ms

Lovelo-Black.woff

Lovelo-Black.woff

863 ms

AvenirNextLTPro-Bold.woff

AvenirNextLTPro-Bold.woff

863 ms

AvenirNextLTPro-Demi.woff

AvenirNextLTPro-Demi.woff

855 ms

AvenirNextLTPro-Medium.woff

AvenirNextLTPro-Medium.woff

853 ms

AvenirNextLTPro-Regular.woff

AvenirNextLTPro-Regular.woff

853 ms

play-button-hover-1.png

play-button-hover-1.png

842 ms

cursor-play.png

cursor-play.png

728 ms

dl-google-play-en.png

dl-google-play-en.png

728 ms

world-map.png

world-map.png

728 ms

icons.woff

icons.woff

652 ms

zasada.gif

zasada.gif

912 ms

btn-app-store-en.svg

btn-app-store-en.svg

736 ms

btn-google-play-en.png

btn-google-play-en.png

528 ms

zarejestruj-sie.png

zarejestruj-sie.png

522 ms

wybieraj.png

wybieraj.png

521 ms

pracodawca.png

pracodawca.png

668 ms

oczekiwania.png

oczekiwania.png

666 ms

callpage.js

callpage.js

392 ms

114a5b858114282a7b218f7144698fca2e20db69.json

114a5b858114282a7b218f7144698fca2e20db69.json

805 ms

iframe_api

iframe_api

359 ms

box-469cf41adb11dc78be68c1ae7f9457a4.html

box-469cf41adb11dc78be68c1ae7f9457a4.html

138 ms

visit-data

visit-data

1195 ms

www-widgetapi.js

www-widgetapi.js

53 ms

smPzPxjql74

smPzPxjql74

121 ms

www-player.css

www-player.css

41 ms

www-embed-player.js

www-embed-player.js

135 ms

base.js

base.js

203 ms

fetch-polyfill.js

fetch-polyfill.js

181 ms

asset-manifest.json

asset-manifest.json

831 ms

ad_status.js

ad_status.js

518 ms

embed.js

embed.js

132 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

144 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

160 ms

Accessibility Review

filttr.pl accessibility score

79

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

filttr.pl best practices score

58

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

filttr.pl SEO score

54

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    PL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Filttr.pl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Polish language. Our system also found out that Filttr.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

filttr.pl

Open Graph data is detected on the main page of FILTTR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: