2.6 sec in total
731 ms
1.7 sec
144 ms
Click here to check amazing Orlik content. Otherwise, check out these important facts you probably never knew about orlik.cz
Snadný a rychlý nákup kompresorů a příslušenství. Vyberte si některý z našich osvědčených kompresorů.
Visit orlik.czWe analyzed Orlik.cz page load time and found that the first response time was 731 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
orlik.cz performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value8.4 s
2/100
25%
Value16.3 s
0/100
10%
Value1,170 ms
21/100
30%
Value0.02
100/100
15%
Value12.6 s
14/100
10%
731 ms
241 ms
484 ms
365 ms
359 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 96% of them (48 requests) were addressed to the original Orlik.cz, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (802 ms) belongs to the original domain Orlik.cz.
Page size can be reduced by 851.0 kB (77%)
1.1 MB
256.8 kB
In fact, the total size of Orlik.cz main page is 1.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. Javascripts take 898.7 kB which makes up the majority of the site volume.
Potential reduce by 43.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 43.4 kB or 71% of the original size.
Potential reduce by 3.1 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, Orlik needs image optimization as it can save up to 3.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 703.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 703.8 kB or 78% of the original size.
Potential reduce by 100.6 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. Orlik.cz needs all CSS files to be minified and compressed as it can save up to 100.6 kB or 85% of the original size.
Number of requests can be reduced by 37 (76%)
49
12
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orlik. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
orlik.cz
731 ms
Site.css
241 ms
StyleSheet.css
484 ms
Button.WebSite.css
365 ms
ComboBox.WebSite.css
359 ms
Dock.WebSite.css
241 ms
Input.WebSite.css
354 ms
ListBox.WebSite.css
483 ms
Menu.WebSite.css
476 ms
Window.WebSite.css
477 ms
Menu.WebSiteMenuMin.css
607 ms
WebResource.axd
590 ms
WebResource.axd
590 ms
WebResource.axd
585 ms
ScriptResource.axd
522 ms
ScriptResource.axd
372 ms
ScriptResource.axd
582 ms
ScriptResource.axd
481 ms
ScriptResource.axd
480 ms
ScriptResource.axd
489 ms
ScriptResource.axd
494 ms
ScriptResource.axd
600 ms
ScriptResource.axd
601 ms
ScriptResource.axd
608 ms
ScriptResource.axd
611 ms
ScriptResource.axd
636 ms
ScriptResource.axd
692 ms
ScriptResource.axd
710 ms
ScriptResource.axd
714 ms
ScriptResource.axd
723 ms
ScriptResource.axd
727 ms
ScriptResource.axd
753 ms
ScriptResource.axd
802 ms
analytics.js
14 ms
page-layout-head-top-center-account.gif
460 ms
Telerik.Web.UI.WebResource.axd
460 ms
Telerik.Web.UI.WebResource.axd
461 ms
logo-orlik.gif
464 ms
Telerik.Web.UI.WebResource.axd
488 ms
Telerik.Web.UI.WebResource.axd
529 ms
Telerik.Web.UI.WebResource.axd
554 ms
Telerik.Web.UI.WebResource.axd
562 ms
page-layout-head-menu-home.gif
573 ms
icon-warning-16x16.gif
580 ms
Telerik.Web.UI.WebResource.axd
605 ms
Telerik.Web.UI.WebResource.axd
640 ms
Telerik.Web.UI.WebResource.axd
669 ms
collect
11 ms
page-layout-head-top-left-bkgn.gif
266 ms
page-layout-head-motto-body.jpg
291 ms
orlik.cz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
orlik.cz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
orlik.cz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
CS
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Orlik.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Orlik.cz 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.
orlik.cz
Open Graph description is not detected on the main page of Orlik. 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: