Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

korex.net.pl

KOREX portal tradycyjnej fotografi

Page Load Speed

4 sec in total

First Response

812 ms

Resources Loaded

2.9 sec

Page Rendered

325 ms

About Website

Click here to check amazing KOREX content for Poland. Otherwise, check out these important facts you probably never knew about korex.net.pl

KOREX - Aktualności, zaproszenia i forum fotograficzne. KOREX - portal tradycyjnej fotografii. fotografia czarno-biała, tradycyjna.

Visit korex.net.pl

Key Findings

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

Performance Metrics

korex.net.pl performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.509

15/100

15%

TTI (Time to Interactive)

Value19.0 s

3/100

10%

Network Requests Diagram

www.korex.net.pl

812 ms

blocks.style.build.css

209 ms

8c889350b96b90c5a6099d57b2048a72.min.css

649 ms

swfobject.js

219 ms

jquery.min.js

327 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 57% of them (24 requests) were addressed to the original Korex.net.pl, 19% (8 requests) were made to Static.xx.fbcdn.net and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (910 ms) belongs to the original domain Korex.net.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 230.3 kB (9%)

Content Size

2.5 MB

After Optimization

2.2 MB

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

HTML Optimization

-77%

Potential reduce by 65.4 kB

  • Original 85.3 kB
  • After minification 82.8 kB
  • After compression 19.9 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 65.4 kB or 77% of the original size.

Image Optimization

-9%

Potential reduce by 163.5 kB

  • Original 1.9 MB
  • After minification 1.7 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. KOREX images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 864 B

  • Original 259.4 kB
  • After minification 259.3 kB
  • After compression 258.5 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

-0%

Potential reduce by 514 B

  • Original 197.9 kB
  • After minification 197.7 kB
  • After compression 197.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. Korex.net.pl has all CSS files already compressed.

Requests Breakdown

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

Requests Now

40

After Optimization

17

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

Accessibility Review

korex.net.pl accessibility score

86

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

korex.net.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

korex.net.pl SEO score

92

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

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 Korex.net.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 Korex.net.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 KOREX. 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: