23.1 sec in total
330 ms
22.5 sec
250 ms
Click here to check amazing Open Office content for Czech Republic. Otherwise, check out these important facts you probably never knew about openoffice.cz
Portál pro uživatele kancelářských balíků OpenOffice a LibreOffice
Visit openoffice.czWe analyzed Openoffice.cz page load time and found that the first response time was 330 ms and then it took 22.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
openoffice.cz performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value15.6 s
0/100
25%
Value11.2 s
5/100
10%
Value1,820 ms
9/100
30%
Value0.154
74/100
15%
Value17.5 s
4/100
10%
330 ms
1608 ms
111 ms
216 ms
318 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 50% of them (54 requests) were addressed to the original Openoffice.cz, 7% (8 requests) were made to Googleads.g.doubleclick.net and 6% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Toplist.cz.
Page size can be reduced by 83.5 kB (5%)
1.6 MB
1.5 MB
In fact, the total size of Openoffice.cz main page is 1.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. 70% of websites need less resources to load. Javascripts take 799.2 kB which makes up the majority of the site volume.
Potential reduce by 45.2 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 45.2 kB or 80% of the original size.
Potential reduce by 18.9 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. Open Office images are well optimized though.
Potential reduce by 15.6 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.
Potential reduce by 3.8 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. Openoffice.cz needs all CSS files to be minified and compressed as it can save up to 3.8 kB or 22% of the original size.
Number of requests can be reduced by 55 (56%)
99
44
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open Office. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
openoffice.cz
330 ms
www.openoffice.cz
1608 ms
main.css
111 ms
inline.css
216 ms
shCore.js
318 ms
shBrushBash.js
328 ms
shBrushJava.js
329 ms
shBrushPython.js
330 ms
shBrushXml.js
328 ms
shCoreDefault.css
330 ms
shThemeDefault.css
422 ms
prototype.js
534 ms
scriptaculous.js
423 ms
qcm.js
425 ms
global.js
423 ms
calendar-blue.css
425 ms
calendar.js
529 ms
calendar-cs.js
528 ms
calendar-setup.js
530 ms
plusone.js
52 ms
api.js
62 ms
js
78 ms
adsbygoogle.js
124 ms
adsbygoogle.js
216 ms
builder.js
121 ms
effects.js
110 ms
dragdrop.js
108 ms
controls.js
109 ms
slider.js
110 ms
sound.js
108 ms
qcmclient.js
108 ms
qcmtools.js
115 ms
load.js
244 ms
cb=gapi.loaded_0
77 ms
recaptcha__en.js
239 ms
03-triada-01.jpg
947 ms
Setkani-t-support-2024-2416.jpg
1196 ms
70582a97ef2ef3f8239b2e63cacc9d4d.png
1073 ms
dot.asp
19753 ms
acer_1.jpg
1050 ms
03-matzner-01.jpg
1196 ms
03-capgemini-01.jpg
1392 ms
NEVO3D-Mgmt_klein-2416.jpg
1393 ms
Sintratec-3Dees-2416.jpg
1744 ms
Doprovodny_program_HM2024-2416.jpg
1799 ms
open-libre-logo.png
223 ms
blank.gif
222 ms
btn_input.gif
222 ms
5944.jpg
222 ms
tdf.png
223 ms
5928.jpg
221 ms
5931.jpg
302 ms
openoffice.jpg
304 ms
5884.jpg
301 ms
item_dash.png
300 ms
6016.jpg
303 ms
month_lo.png
349 ms
office365.png
349 ms
installfest_s.png
348 ms
5983.jpg
350 ms
stahnout_lo2.png
350 ms
stahnout-LO-pro_android2.png
351 ms
stahnout-LO_Impress_Remote2.png
435 ms
stahnout_oo2.png
436 ms
stahnout_slovniky2.png
437 ms
stahnout_doplnky2.png
436 ms
stahnout_manualy_a_prirucky2.png
438 ms
stahnout_sablony2.png
437 ms
dot.asp
19748 ms
dot.asp
19748 ms
dot.asp
19749 ms
show_ads_impl.js
457 ms
bublina-komentare.png
367 ms
pozadi_doporucujeme.png
299 ms
analytics.js
6 ms
collect
23 ms
collect
41 ms
collect
31 ms
collect
31 ms
js
39 ms
js
54 ms
js
51 ms
print.css
204 ms
zrt_lookup.html
67 ms
ads
152 ms
ads
418 ms
ads
328 ms
ads
483 ms
ads
673 ms
handheld.css
108 ms
ca-pub-2826757030954706
71 ms
c9cd4a097b15def18816fa5d93e4cd4f.js
7 ms
3b0c1a1c8750041eb27603629860e89a.js
21 ms
load_preloaded_resource.js
84 ms
cdf01d8369ba0e15ccbc9395c59a9391.js
53 ms
f11bfab4e3c942216447974439595ef6.js
57 ms
abg_lite.js
216 ms
window_focus.js
253 ms
qs_click_protection.js
84 ms
ufs_web_display.js
77 ms
bbae3fd3506d8d9338f85d10ea9db8af.js
78 ms
icon.png
46 ms
s
175 ms
css
58 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
19 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
24 ms
activeview
91 ms
12jlMzyD-2VTuBGWfQdcv4sHjYqKdk-jjJ1uxYEhkwQ.js
6 ms
openoffice.cz 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-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
openoffice.cz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
openoffice.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
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Openoffice.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it matches the claimed language. Our system also found out that Openoffice.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.
openoffice.cz
Open Graph description is not detected on the main page of Open Office. 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: