4.5 sec in total
355 ms
3.8 sec
358 ms
Visit s6.o2.sk now to see the best up-to-date S 6 O2 content for Slovakia and also check out these interesting facts you probably never knew about s6.o2.sk
Mobilné telefóny, tablety, modemy a príslušenstvo v O2 E-shope.
Visit s6.o2.skWe analyzed S6.o2.sk page load time and found that the first response time was 355 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
s6.o2.sk performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value14.2 s
0/100
25%
Value12.5 s
3/100
10%
Value3,110 ms
2/100
30%
Value1.057
2/100
15%
Value18.0 s
3/100
10%
355 ms
330 ms
676 ms
529 ms
418 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original S6.o2.sk, 34% (46 requests) were made to O2static.sk and 25% (34 requests) were made to O2.sk. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source O2static.sk.
Page size can be reduced by 654.5 kB (51%)
1.3 MB
624.2 kB
In fact, the total size of S6.o2.sk main page is 1.3 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 664.8 kB which makes up the majority of the site volume.
Potential reduce by 167.6 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 33.9 kB, which is 17% 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 167.6 kB or 86% of the original size.
Potential reduce by 207.6 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, S 6 O2 needs image optimization as it can save up to 207.6 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 279.3 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 279.3 kB or 67% of the original size.
Number of requests can be reduced by 89 (68%)
131
42
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of S 6 O2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
s6.o2.sk
355 ms
330 ms
676 ms
css.jsp
529 ms
portlet.css
418 ms
colorbox.css
422 ms
hw-detail.css
424 ms
minihwcomparison.css
425 ms
liferay.css+layout.css+content.css+dockbar.css+eshop-cart.css+footer.css+jquery-ui-1.10.4.custom.min.css+font-awesome.css+jquery.fancybox.css+jquery.fancybox-buttons.css+jquery.fancybox-thumbs.css+select2.css+icons.css+main_menu.css+bootstrap.min.css+bootstrap-select.min.css+bootstrap-o2-custom.css+bootstrap-multiselect.css+captcha.css.pagespeed.cc.A_LZNczp1k.css
874 ms
tablet.css
535 ms
desktop.css
537 ms
A.shCore.css+shThemeDefault.css,Mcc.Fc56mgGgmR.css.pagespeed.cf.HtEHGAHhkC.css
539 ms
everything.jsp,qbrowserId=other,athemeId=mojeO2_WAR_liferaytheme,acolorSchemeId=01,aminifierType=js,aminifierBundleId=javascript.everything.files,alanguageId=sk_SK,ab=6011,at=1457047399000.pagespeed.jm.FlMHhMl0nf.js
1130 ms
hw-detail.js
224 ms
programAndMPlusDropdown.js
226 ms
minihwcomparison.js
231 ms
jquery2.map.js+jquery.validate.min.js+validator.methods.js+ajax.js.pagespeed.jc.7-oyHcZacW.js
638 ms
main.js+bootstrap-select.custom.js.pagespeed.jc.wrvqf4LdCG.js
646 ms
bootstrap-multiselect.js+bootstrap-tabcollapse.js+bootstrap.min.js.pagespeed.jc.RkZviUhPXx.js
653 ms
jquery-ui-1.10.4.custom.min.js.pagespeed.jm.ndvv-XkOIo.js
1011 ms
jquery.ui.datepicker-sk.js+jquery.ui.touch-punch.min.js.pagespeed.jc.aZTpAgAb8m.js
748 ms
jquery.fixedheadertable.min.js.pagespeed.jm.Fotjw1lQB-.js
758 ms
jquery.touchSwipe.min.js.pagespeed.jm.LmwRc3fI9_.js
768 ms
jquery.iframe-transport.js+jquery.fileupload.js+fancybox,_jquery.mousewheel.pack.js.pagespeed.jc.eRaLtdTBNr.js
859 ms
fancybox,_jquery.fancybox.pack.js+fancybox,_jquery.fancybox-media.js+fancybox,_jquery.fancybox-buttons.js+fancybox,_jquery.fancybox-thumbs.js+captcha.js+sessionStorageO2.js+script.js+eportal-componentsinit.js.pagespeed.jc.pSbFh-bVyd.js
985 ms
jquery.dataTables.min.js+jquery.dataTables.bootstrap.js+jquery-datatables-guidelines-pagination.js.pagespeed.jc.xmlF1JcPAt.js
1001 ms
storedockbar.js.pagespeed.jm.LZhTPsWlCv.js
226 ms
trackchat.js
452 ms
js,_typeahead.bundle.min.js+js,_main_menu.js+js,_address-suggestor.js+js,_authentication.js+javascript,_touchscreen_menu.js+js,_shCore.js+js,_shBrushXml.js.pagespeed.jc.pJcBe6CfGL.js
981 ms
jquery.colorbox.js
132 ms
ajaxUI.js
229 ms
lazySelectpicker.js
233 ms
jquery.ajax-loader.js
231 ms
main.js,qbrowserId=other,aminifierType=js,alanguageId=sk_SK,ab=6011,at=1456271067000.pagespeed.jm.aVfvRiohkU.js
878 ms
OpenSans.woff
126 ms
OpenSans-Light.woff
456 ms
OpenSans-Semibold.woff
457 ms
background-bg.png
132 ms
gtm.js
105 ms
mobilne-zariadenia
571 ms
mobile-menu-button.png
372 ms
logo.svg
368 ms
mobile-mojeo2-menu-button.png
374 ms
small-shopping-cart-new.jpg
377 ms
xbeztelky_menubanner.png.pagespeed.ic.RAHP_8LgyZ.png
379 ms
niecoextra_menubanner.png
370 ms
x4g.jpg.pagespeed.ic.jPRIHeibeZ.jpg
368 ms
xmobilna_appka_menu.jpg.pagespeed.ic.9gGOCGIdyJ.jpg
369 ms
xev-textbox.jpg.pagespeed.ic.rWSUrS8FiM.jpg
369 ms
breadcrumbs-divider.png
370 ms
detail-comparison-ico-mock.png
361 ms
259-detail-image.png
919 ms
263-detail-image.png
870 ms
262-detail-image.png
513 ms
261-detail-image.png
552 ms
264-detail-image.png
802 ms
259-preview-small-image.png
373 ms
263-preview-small-image.png
514 ms
262-preview-small-image.png
546 ms
261-preview-small-image.png
604 ms
264-preview-small-image.png
727 ms
-202-preview-middle-image.png
725 ms
2140-basket-middle-image.jpg
795 ms
925-basket-middle-image.jpg
835 ms
-1001113-basket-middle-image.jpeg
834 ms
-1001040-basket-middle-image.jpeg
911 ms
glyphicons-halflings-regular.woff
370 ms
sdk.js
93 ms
question-mark.png
339 ms
play-icon.png
342 ms
star-off-big.png
343 ms
dropdown-box-up-btn.png
345 ms
dropdown-box-down-btn.png
347 ms
checkmark.png
348 ms
arrow-back.png
481 ms
arrow.png
482 ms
466 ms
dc.js
198 ms
conversion_async.js
194 ms
3751.js
198 ms
fbevents.js
191 ms
585 ms
gemius.js
377 ms
oct.js
191 ms
analytics.js
182 ms
hmapxy.js
760 ms
list-bullet.jpg
193 ms
mobile-mojeo2-menu-button-14px.png
191 ms
overlay.png
192 ms
guru-online-chat.png
561 ms
xofflinebuttons2.png.pagespeed.ic.NI-1Au4r3H.png
615 ms
tags
351 ms
fontawesome-webfont.woff
568 ms
158 ms
267 ms
__utm.gif
63 ms
ec.js
53 ms
adsct
349 ms
adsct
215 ms
tags
286 ms
s
313 ms
u
263 ms
257 ms
257 ms
xd_arbiter.php
188 ms
xd_arbiter.php
349 ms
ga-audiences
292 ms
collect
109 ms
fpdata.js
227 ms
lsget.html
346 ms
247 ms
242 ms
UserMatch.ashx
111 ms
pixel
327 ms
168 ms
RtbHouse
325 ms
match
111 ms
tagging
132 ms
Pug
132 ms
221 ms
match
49 ms
Pug
46 ms
UserMatch.ashx
25 ms
69 ms
RtbHouse
232 ms
pixel
230 ms
sd
32 ms
sd
25 ms
ga-audiences
27 ms
cm
105 ms
cm
101 ms
1by1.png
16 ms
tap.php
132 ms
tap.php
122 ms
1by1.png
11 ms
redot.js
120 ms
s6.o2.sk accessibility score
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
ARIA input fields do not have accessible names
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
Form elements do not have associated labels
Links do not have a discernible name
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.
s6.o2.sk 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
s6.o2.sk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
SK
SK
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise S6.o2.sk can be misinterpreted by Google and other search engines. Our service has detected that Slovak is used on the page, and it matches the claimed language. Our system also found out that S6.o2.sk main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
s6.o2.sk
Open Graph description is not detected on the main page of S 6 O2. 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: