Tools & Wizards About Us
xml-director.info screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    41% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

xml-director.info

XML Content Management System / XML-Director / The open-source XML content management system CMS

Page Load Speed

8.5 sec in total

First Response

315 ms

Resources Loaded

6.2 sec

Page Rendered

2 sec

xml-director.info screenshot

About Website

Click here to check amazing XML Director content. Otherwise, check out these important facts you probably never knew about xml-director.info

A XML content management system based on the CMS Plone for XML content, DOCX to XML conversion and high-quality PDF production, EPUB support. Enterprise CMS.

Visit xml-director.info

Key Findings

We analyzed Xml-director.info page load time and found that the first response time was 315 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

xml-director.info performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value2,180 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value15.8 s

6/100

10%

Network Requests Diagram

xml-director.info

315 ms

www.xml-director.info

557 ms

modernizr.js

187 ms

bootstrap.min.css

305 ms

styles.css

346 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 74% of them (63 requests) were addressed to the original Xml-director.info, 8% (7 requests) were made to Youtube.com and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Xml-director.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (64%)

Content Size

2.1 MB

After Optimization

764.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xml-director.info main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 745.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 309.0 kB

  • Original 430.8 kB
  • After minification 377.1 kB
  • After compression 121.8 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 53.7 kB, which is 12% 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 309.0 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 40 B

  • Original 295.6 kB
  • After minification 295.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. XML Director images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 532.3 kB

  • Original 745.5 kB
  • After minification 611.1 kB
  • After compression 213.2 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 532.3 kB or 71% of the original size.

CSS Optimization

-79%

Potential reduce by 512.8 kB

  • Original 646.9 kB
  • After minification 633.9 kB
  • After compression 134.1 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. Xml-director.info needs all CSS files to be minified and compressed as it can save up to 512.8 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (49%)

Requests Now

78

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of XML Director. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

xml-director.info

xml-director.info

315 ms

www.xml-director.info

www.xml-director.info

557 ms

modernizr.js

modernizr.js

187 ms

bootstrap.min.css

bootstrap.min.css

305 ms

styles.css

styles.css

346 ms

style.css

style.css

412 ms

font-awesome.css

font-awesome.css

415 ms

fonts.css

fonts.css

362 ms

Hyphenator.js

Hyphenator.js

694 ms

jquery.min.js

jquery.min.js

529 ms

bootstrap.min.js

bootstrap.min.js

475 ms

retina.js

retina.js

390 ms

jquery.scrollto.min.js

jquery.scrollto.min.js

442 ms

jquery.easing.js

jquery.easing.js

451 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

495 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

747 ms

smoothscroll.js

smoothscroll.js

555 ms

jquery.localscroll.min.js

jquery.localscroll.min.js

576 ms

imagesloaded.min.js

imagesloaded.min.js

598 ms

skrollr.js

skrollr.js

632 ms

ekko-lightbox.min.js

ekko-lightbox.min.js

656 ms

jquery.backstretch.min.js

jquery.backstretch.min.js

675 ms

jquery.gmap.min.js

jquery.gmap.min.js

700 ms

jquery.form.js

jquery.form.js

728 ms

jquery.flowuplabels.js

jquery.flowuplabels.js

731 ms

custom.js

custom.js

771 ms

jquery.rss.min.js

jquery.rss.min.js

785 ms

steadysets.css

steadysets.css

470 ms

linecons.css

linecons.css

617 ms

et-line.css

et-line.css

501 ms

videoseries

videoseries

2282 ms

xml-director-logo.svg

xml-director-logo.svg

2261 ms

intro_bg.jpg

intro_bg.jpg

2258 ms

xml-director-logo-inverted.svg

xml-director-logo-inverted.svg

2258 ms

docx2xml.png

docx2xml.png

2251 ms

xml-workflows.png

xml-workflows.png

2246 ms

pdf-layouts.png

pdf-layouts.png

2244 ms

works_bg.jpg

works_bg.jpg

2495 ms

usecases.png

usecases.png

2512 ms

unified-xml-workflows.png

unified-xml-workflows.png

2530 ms

claim-pdf-layouts.png

claim-pdf-layouts.png

2530 ms

plone-logo.svg

plone-logo.svg

2513 ms

plone-5-screen.png

plone-5-screen.png

3100 ms

existdb.svg

existdb.svg

2733 ms

basex.svg

basex.svg

2740 ms

openness.png

openness.png

3008 ms

platform.png

platform.png

3008 ms

dita-logo.jpg

dita-logo.jpg

3008 ms

web2print.png

web2print.png

3008 ms

zoom.png

zoom.png

3211 ms

alternative-banner.jpg

alternative-banner.jpg

3099 ms

new-uniquebg.jpg

new-uniquebg.jpg

3198 ms

york.png

york.png

3084 ms

vs.jpg

vs.jpg

3084 ms

locandy.png

locandy.png

3198 ms

dgho.png

dgho.png

3197 ms

osha.jpg

osha.jpg

3198 ms

team_bg.jpg

team_bg.jpg

3280 ms

andreasjung-rounded.png

andreasjung-rounded.png

3435 ms

@.png

@.png

3413 ms

Twitter.png

Twitter.png

3426 ms

YouTube.png

YouTube.png

3278 ms

RSS.png

RSS.png

3434 ms

mem8YaGs126MiZpBA-UFVZ0e.ttf

mem8YaGs126MiZpBA-UFVZ0e.ttf

2020 ms

mem5YaGs126MiZpBA-UN_r8OUuhs.ttf

mem5YaGs126MiZpBA-UN_r8OUuhs.ttf

2020 ms

mem5YaGs126MiZpBA-UN7rgOUuhs.ttf

mem5YaGs126MiZpBA-UN7rgOUuhs.ttf

2043 ms

widgets.js

widgets.js

2868 ms

matomo.js

matomo.js

2783 ms

www-player.css

www-player.css

158 ms

www-embed-player.js

www-embed-player.js

229 ms

base.js

base.js

305 ms

fetch-polyfill.js

fetch-polyfill.js

293 ms

ad_status.js

ad_status.js

371 ms

list_ajax

list_ajax

459 ms

embed.js

embed.js

99 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

68 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

68 ms

widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html

widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html

39 ms

matomo.php

matomo.php

816 ms

id

id

128 ms

settings

settings

263 ms

moment~timeline~tweet.ae149926685a43cb146e35371430188e.js

moment~timeline~tweet.ae149926685a43cb146e35371430188e.js

58 ms

timeline.687eed636a16648c9f0b1f72d7fa68bd.js

timeline.687eed636a16648c9f0b1f72d7fa68bd.js

58 ms

profile

profile

195 ms

en-us.js

en-us.js

207 ms

Accessibility Review

xml-director.info accessibility score

78

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

xml-director.info best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

xml-director.info SEO score

89

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xml-director.info 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 Xml-director.info 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.

Social Sharing Optimization

xml-director.info

Open Graph description is not detected on the main page of XML Director. 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: