10.4 sec in total
243 ms
9.9 sec
251 ms
Visit xwiki.com now to see the best up-to-date XWiki content for Ukraine and also check out these interesting facts you probably never knew about xwiki.com
Home of the XWiki and CryptPad Open Source projects. Looking to organize your information better? XWiki SAS's team of professionals is the best solution for you and your team. Ready-to-use or Cust...
Visit xwiki.comWe analyzed Xwiki.com page load time and found that the first response time was 243 ms and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
xwiki.com performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value15.5 s
0/100
25%
Value14.6 s
1/100
10%
Value1,910 ms
8/100
30%
Value0.208
60/100
15%
Value32.6 s
0/100
10%
243 ms
80 ms
1985 ms
14 ms
207 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 83% of them (127 requests) were addressed to the original Xwiki.com, 3% (5 requests) were made to Info.xwiki.com and 3% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Xwiki.com.
Page size can be reduced by 344.7 kB (68%)
504.3 kB
159.6 kB
In fact, the total size of Xwiki.com main page is 504.3 kB. 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 340.5 kB which makes up the majority of the site volume.
Potential reduce by 131.1 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 131.1 kB or 90% of the original size.
Potential reduce by 0 B
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. XWiki images are well optimized though.
Potential reduce by 199.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 199.6 kB or 59% of the original size.
Potential reduce by 13.9 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. Xwiki.com needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 82% of the original size.
Number of requests can be reduced by 75 (53%)
141
66
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of XWiki. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
xwiki.com
243 ms
80 ms
1985 ms
munchkin.js
14 ms
mixpanel-2-latest.min.js
207 ms
style.css
289 ms
xwiki-min.css
177 ms
searchSuggest.css
173 ms
Code
172 ms
Settings
181 ms
TopMenu
175 ms
Style
300 ms
Script
298 ms
Style
412 ms
FontAwesome
3088 ms
HeaderV2
301 ms
MenuV2
364 ms
MenuMacro
367 ms
DisplayerMacros
362 ms
TotemFullscreen
387 ms
CarouselDisplayerXWikiCom
3073 ms
ImageOnTop2
3062 ms
SimpleText
3059 ms
ImageOnTop
3062 ms
MultImgCarouselDisplayer2
3075 ms
CarouselDisplayerMobile
3153 ms
TextOnFullImageVideo
3150 ms
TextOnFullImage
3149 ms
IntelImageMobile
3157 ms
Sectionlink
3155 ms
require.js
3167 ms
prototype.js
3323 ms
effects.js
3262 ms
xwiki-min.js
3400 ms
searchSuggest.js
3398 ms
Script
3492 ms
Code
3260 ms
Settings
3343 ms
GoogleAnalyticsCode
3348 ms
TopMenu
3492 ms
munchkin.js
3 ms
visitWebPage
168 ms
forms2.min.js
488 ms
Script
3432 ms
EncryptedEmail
3330 ms
MenuV2
3371 ms
MenuMacro
3327 ms
TotemSheet
3367 ms
CarouselDisplayerXWikiCom
3364 ms
69 ms
widget_v2.134.js
8 ms
HomeVideo
3262 ms
MultImgCarouselDisplayer2
3262 ms
CarouselDisplayerMobile
3298 ms
TextOnFullImageVideo
3308 ms
Style
3257 ms
compatibility.js
3330 ms
markerScript.js
3312 ms
css
22 ms
css
35 ms
css
43 ms
email-black.png
342 ms
butonxwiki.png
341 ms
menu-bg.png
341 ms
logo-blanc.png
351 ms
logo.png
343 ms
test-bg.jpg
351 ms
test-button-en.png
486 ms
bgMenu.jpg
419 ms
812 ms
slider1.jpg
864 ms
plus.png
509 ms
slide2.jpg
1337 ms
slide3.jpg
1397 ms
buttons-h-bg.png
655 ms
icon-test-retina-en.png
657 ms
icon-play-retina.png
801 ms
icon-contact-retina.png
802 ms
email-button.png
897 ms
busines-case-4.jpg
896 ms
path
1222 ms
busines-case-1.jpg
903 ms
busines-case-2.jpg
1196 ms
busines-case-3.jpg
1196 ms
plusblue.png
1206 ms
getForm
468 ms
pq-xwiki.jpg
1168 ms
deploiment.jpg
1167 ms
kitmedia.jpg
1230 ms
path
1237 ms
K6ngFdK5haaaRGBV8waDwA.ttf
44 ms
187TYb8ysVvxar86IcDsZ_esZW2xOQ-xsNqO47m55DA.ttf
65 ms
TNtGAwzXtCEY_5hzRlIJNPesZW2xOQ-xsNqO47m55DA.ttf
76 ms
nHiQo1BypvYzt95zlPq1TvesZW2xOQ-xsNqO47m55DA.ttf
74 ms
aba341ac-5d80-4545-a62b-7541192e810d.js
20 ms
analytics.js
20 ms
path
1192 ms
bgclients.jpg
1214 ms
jquery.min.js
42 ms
collect
21 ms
afcen.jpg
1544 ms
collect
169 ms
afp.jpg
1588 ms
aelia.jpg
1504 ms
brabantia.jpg
1818 ms
a.gif
485 ms
path
1127 ms
path
1171 ms
caphc.jpg
1887 ms
cnfpt.jpg
1762 ms
capgemini.jpg
2171 ms
chronopost.jpg
2199 ms
credit-mutuel-arkea.jpg
2185 ms
curriki.jpg
2185 ms
dcns.jpg
2126 ms
edf.jpg
2069 ms
emc.jpg
2108 ms
forms2.css
82 ms
forms2-theme-round.css
161 ms
easy-vista.jpg
2121 ms
energisa.jpg
2083 ms
XDFrame
482 ms
expert-finance.jpg
1931 ms
fnab.jpg
1942 ms
foph.jpg
1969 ms
fidelia-assistance.jpg
1917 ms
inra.png
1936 ms
insee.jpg
1940 ms
iwa-publishing.jpg
1882 ms
avatar_simple_visitor.png
79 ms
meetic.jpg
1683 ms
noiv.jpg
1738 ms
ow2.jpg
1705 ms
sankore.jpg
1736 ms
premier-league.jpg
1733 ms
Numericable.png
2082 ms
aL63HcygAAVYuCCsAAA==
23 ms
socomore.jpg
1705 ms
spie-batignolles.jpg
1735 ms
ush.jpg
1754 ms
voyage-prive.jpg
1760 ms
vulco.jpg
1740 ms
slider1-mobile.jpg
1895 ms
slider2-mobile-2.jpg
2016 ms
slider3-mobile-2.jpg
1980 ms
videoEN.jpg
1587 ms
service1.jpg
1640 ms
service2.jpg
1686 ms
email-gray.png
1344 ms
logow.png
1350 ms
viadeo.png
1224 ms
buttonXWiki.png
969 ms
print.css
91 ms
xwiki.com 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
Buttons do not have an accessible name
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
xwiki.com 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
Page has valid source maps
xwiki.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xwiki.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Xwiki.com 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.
xwiki.com
Open Graph description is not detected on the main page of XWiki. 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: