10.6 sec in total
1.7 sec
8.6 sec
344 ms
Click here to check amazing Omni content. Otherwise, check out these important facts you probably never knew about omni.pl
OVHcloud accompagne votre évolution grâce au meilleur des infrastructures web : hébergement, nom de domaine, serveur dédié, CDN, Cloud, Big Data, ...
Visit omni.plWe analyzed Omni.pl page load time and found that the first response time was 1.7 sec and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
omni.pl performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value3.4 s
66/100
25%
Value4.0 s
80/100
10%
Value420 ms
66/100
30%
Value0.073
95/100
15%
Value3.8 s
89/100
10%
1705 ms
300 ms
292 ms
213 ms
36 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 84% of them (80 requests) were addressed to the original Omni.pl, 8% (8 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain Omni.pl.
Page size can be reduced by 1.6 MB (58%)
2.7 MB
1.1 MB
In fact, the total size of Omni.pl main page is 2.7 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. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 52.5 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 52.5 kB or 80% of the original size.
Potential reduce by 59.3 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. Omni images are well optimized though.
Potential reduce by 719.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 719.5 kB or 71% of the original size.
Potential reduce by 759.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. Omni.pl needs all CSS files to be minified and compressed as it can save up to 759.4 kB or 88% of the original size.
Number of requests can be reduced by 69 (80%)
86
17
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Omni. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
omni.pl
1705 ms
wp-emoji-release.min.js
300 ms
cache.skin.css
292 ms
styles.css
213 ms
jquery-ui.min.css
36 ms
jquery-ui-timepicker-addon.min.css
223 ms
settings.css
319 ms
font-awesome.min.css
323 ms
jkreativ-icon.min.css
323 ms
style.css
409 ms
plugin.css
399 ms
main.css
692 ms
boxed.css
421 ms
transparent.css
416 ms
jmegamenu.css
421 ms
mediaelementplayer.min.css
572 ms
responsive.css
580 ms
css
70 ms
css
83 ms
css
98 ms
js_composer.css
787 ms
jquery.js
761 ms
jquery-migrate.min.js
615 ms
jquery.themepunch.tools.min.js
877 ms
jquery.themepunch.revolution.min.js
892 ms
flexslider.css
612 ms
jquery.form.min.js
732 ms
scripts.js
718 ms
core.min.js
766 ms
datepicker.min.js
778 ms
jquery.ui.datepicker-pl.min.js
12 ms
jquery-ui-timepicker-addon.min.js
923 ms
jquery-ui-timepicker-pl.js
839 ms
widget.min.js
854 ms
mouse.min.js
871 ms
slider.min.js
871 ms
button.min.js
932 ms
jquery-ui-sliderAccess.js
954 ms
retina.min.js
960 ms
jquery.jcommon.js
979 ms
main.js
900 ms
mediaelement-and-player.min.js
1190 ms
essencialplugin.js
1012 ms
smoothscroll.js
977 ms
jquery.jpageload.js
970 ms
nprogress.js
952 ms
comment-reply.min.js
974 ms
jquery.sharrre.min.js
1087 ms
fotorama.js
1010 ms
style.css
957 ms
bootstrap.js
1020 ms
klass.min.js
1014 ms
code.photoswipe.jquery-3.0.5.1.min.js
1061 ms
jquery.jresponsive360.js
999 ms
jquery.jnormalblog.js
936 ms
jquery.jtooltip.js
927 ms
jquery.slitslider.js
953 ms
infobubble.js
839 ms
owl.carousel.min.js
839 ms
waypoints.js
839 ms
jquery.isotope.min.js
798 ms
jquery.jnpslider.js
788 ms
jquery.magnific-popup.min.js
776 ms
jquery.typer.js
782 ms
odometer.min.js
827 ms
jquery.tubular.1.0.js
806 ms
jquery.jlanding.js
804 ms
menu_functions.js
795 ms
js_composer_front.js
760 ms
jquery.flexslider-min.js
771 ms
grid_noise.png
497 ms
omni-logo-ma%C5%82e.png
495 ms
OMNI-baner-nowy-2.jpg
1048 ms
back_home1.jpg
818 ms
Fotolia_60270814_Subscription_Monthly_M.jpg
1230 ms
omnible.jpg
5736 ms
omni-b%C4%85belki.jpg
1833 ms
g30.png
562 ms
geometric.png
867 ms
-SXnV4mZjf4oh1IBw13WZw.woff
67 ms
ZzUearZLklGfoL18Ti0GaQ.woff
75 ms
fontawesome-webfont.woff
983 ms
2NBgzUtEeyB-Xtpr9bm1CZa6Tn9fxpDPuRSK4Gn5Ybw.woff
46 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
46 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
75 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
75 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
75 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
76 ms
iframe_api
27 ms
www-widgetapi.js
7 ms
coloredbg.png
513 ms
bullet.png
614 ms
large_left.png
683 ms
large_right.png
709 ms
flexslider-icon.woff
714 ms
omni.pl accessibility score
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
omni.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
omni.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
robots.txt is not valid
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
FR
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Omni.pl can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed Polish language. Our system also found out that Omni.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.
omni.pl
Open Graph description is not detected on the main page of Omni. 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: