Tools & Wizards About Us

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

forum.discoparty.pl

Disco Polo - DiscoParty.pl - Słuchaj radio online!

Page Load Speed

5.5 sec in total

First Response

457 ms

Resources Loaded

4.4 sec

Page Rendered

673 ms

About Website

Welcome to forum.discoparty.pl homepage info - get ready to check Forum Disco Party best content for Poland right away, or after learning these important things about forum.discoparty.pl

Słuchaj disco polo online! Radio discoparty.pl - Najlepsze hity disco polo na żywo! Pozdrawiaj swoich znajomych i baw się z nami!

Visit forum.discoparty.pl

Key Findings

We analyzed Forum.discoparty.pl page load time and found that the first response time was 457 ms and then it took 5 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

forum.discoparty.pl performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value5,770 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.23

54/100

15%

TTI (Time to Interactive)

Value32.9 s

0/100

10%

Network Requests Diagram

forum.discoparty.pl

457 ms

forum.discoparty.pl

445 ms

672 ms

style.css

108 ms

styles.css

217 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Forum.discoparty.pl, 79% (103 requests) were made to Discoparty.pl and 5% (6 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Discoparty.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (43%)

Content Size

5.6 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forum.discoparty.pl main page is 5.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 113.3 kB

  • Original 133.3 kB
  • After minification 128.4 kB
  • After compression 20.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. 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 113.3 kB or 85% of the original size.

Image Optimization

-49%

Potential reduce by 2.2 MB

  • Original 4.5 MB
  • After minification 2.3 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, Forum Disco Party needs image optimization as it can save up to 2.2 MB or 49% 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 51.5 kB

  • Original 777.3 kB
  • After minification 777.3 kB
  • After compression 725.8 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.5 kB

  • Original 157.9 kB
  • After minification 157.6 kB
  • After compression 155.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. Forum.discoparty.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 92 (75%)

Requests Now

122

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

forum.discoparty.pl accessibility score

64

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-*] attributes do not match their roles

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

[id] attributes on active, focusable elements are not unique

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

forum.discoparty.pl best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

forum.discoparty.pl SEO score

84

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

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 Forum.discoparty.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 Forum.discoparty.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 data is detected on the main page of Forum Disco Party. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: