Tools & Wizards About Us
xml-director.info screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

xml-director.info

XML-Director — Unified XML Content Workflows

Page Load Speed

6.4 sec in total

First Response

260 ms

Resources Loaded

5.2 sec

Page Rendered

941 ms

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

XML-Director provides DOCX to XML workflows, PDF publishing, and developer tooling powered by Plone and Flowbite.

Visit xml-director.info

Key Findings

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

Performance Metrics

xml-director.info performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value2,730 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value23.3 s

1/100

10%

Network Requests Diagram

xml-director.info

260 ms

www.xml-director.info

578 ms

modernizr.js

205 ms

bootstrap.min.css

405 ms

styles.css

304 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 62% of them (63 requests) were addressed to the original Xml-director.info, 18% (18 requests) were made to Platform.twitter.com and 5% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Xml-director.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 464.4 kB (23%)

Content Size

2.1 MB

After Optimization

1.6 MB

  • 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. Only a small number of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 309.6 kB

  • Original 432.1 kB
  • After minification 378.3 kB
  • After compression 122.4 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.6 kB or 72% of the original size.

Image Optimization

-11%

Potential reduce by 124.0 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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, XML Director needs image optimization as it can save up to 124.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-9%

Potential reduce by 29.0 kB

  • Original 339.9 kB
  • After minification 339.9 kB
  • After compression 310.9 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.

CSS Optimization

-1%

Potential reduce by 1.8 kB

  • Original 146.5 kB
  • After minification 146.5 kB
  • After compression 144.7 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 51 (54%)

Requests Now

94

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 94 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 44 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

260 ms

www.xml-director.info

www.xml-director.info

578 ms

modernizr.js

modernizr.js

205 ms

bootstrap.min.css

bootstrap.min.css

405 ms

styles.css

styles.css

304 ms

style.css

style.css

301 ms

font-awesome.css

font-awesome.css

303 ms

fonts.css

fonts.css

305 ms

Hyphenator.js

Hyphenator.js

409 ms

jquery.min.js

jquery.min.js

413 ms

bootstrap.min.js

bootstrap.min.js

308 ms

retina.js

retina.js

306 ms

jquery.scrollto.min.js

jquery.scrollto.min.js

306 ms

jquery.easing.js

jquery.easing.js

406 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

407 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

412 ms

smoothscroll.js

smoothscroll.js

408 ms

jquery.localscroll.min.js

jquery.localscroll.min.js

413 ms

imagesloaded.min.js

imagesloaded.min.js

505 ms

skrollr.js

skrollr.js

506 ms

ekko-lightbox.min.js

ekko-lightbox.min.js

508 ms

jquery.backstretch.min.js

jquery.backstretch.min.js

510 ms

jquery.gmap.min.js

jquery.gmap.min.js

511 ms

jquery.form.js

jquery.form.js

515 ms

jquery.flowuplabels.js

jquery.flowuplabels.js

603 ms

custom.js

custom.js

606 ms

jquery.rss.min.js

jquery.rss.min.js

607 ms

steadysets.css

steadysets.css

406 ms

linecons.css

linecons.css

520 ms

et-line.css

et-line.css

415 ms

videoseries

videoseries

1902 ms

xml-director-logo.svg

xml-director-logo.svg

165 ms

intro_bg.jpg

intro_bg.jpg

1889 ms

xml-director-logo-inverted.svg

xml-director-logo-inverted.svg

163 ms

docx2xml.png

docx2xml.png

1889 ms

xml-workflows.png

xml-workflows.png

165 ms

pdf-layouts.png

pdf-layouts.png

165 ms

works_bg.jpg

works_bg.jpg

1887 ms

usecases.png

usecases.png

1888 ms

unified-xml-workflows.png

unified-xml-workflows.png

1888 ms

claim-pdf-layouts.png

claim-pdf-layouts.png

1888 ms

plone-logo.svg

plone-logo.svg

2007 ms

plone-5-screen.png

plone-5-screen.png

2516 ms

existdb.svg

existdb.svg

1998 ms

basex.svg

basex.svg

2008 ms

openness.png

openness.png

2320 ms

platform.png

platform.png

2320 ms

dita-logo.jpg

dita-logo.jpg

2319 ms

web2print.png

web2print.png

2320 ms

zoom.png

zoom.png

2515 ms

alternative-banner.jpg

alternative-banner.jpg

2352 ms

new-uniquebg.jpg

new-uniquebg.jpg

2514 ms

york.png

york.png

2351 ms

vs.jpg

vs.jpg

2350 ms

locandy.png

locandy.png

2515 ms

dgho.png

dgho.png

2516 ms

osha.jpg

osha.jpg

2515 ms

team_bg.jpg

team_bg.jpg

2639 ms

andreasjung-rounded.png

andreasjung-rounded.png

2697 ms

@.png

@.png

2640 ms

Twitter.png

Twitter.png

2640 ms

YouTube.png

YouTube.png

2641 ms

RSS.png

RSS.png

2641 ms

mem8YaGs126MiZpBA-UFVZ0e.ttf

mem8YaGs126MiZpBA-UFVZ0e.ttf

1748 ms

mem5YaGs126MiZpBA-UN_r8OUuhs.ttf

mem5YaGs126MiZpBA-UN_r8OUuhs.ttf

1840 ms

mem5YaGs126MiZpBA-UN7rgOUuhs.ttf

mem5YaGs126MiZpBA-UN7rgOUuhs.ttf

1878 ms

widgets.js

widgets.js

1730 ms

matomo.js

matomo.js

2439 ms

www-player.css

www-player.css

59 ms

www-embed-player.js

www-embed-player.js

124 ms

base.js

base.js

178 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

93 ms

settings

settings

358 ms

ad_status.js

ad_status.js

160 ms

hkwQPN6l4_SNpHVtjw8vAhWItmV3wkCVMuKaKCsfQ0c.js

hkwQPN6l4_SNpHVtjw8vAhWItmV3wkCVMuKaKCsfQ0c.js

148 ms

embed.js

embed.js

59 ms

AIdro_kaWV_k_qwH-xbJ2StfFCBGfanBeAyVE5pTUpXOl2zVQuk=s68-c-k-c0x00ffffff-no-rj

AIdro_kaWV_k_qwH-xbJ2StfFCBGfanBeAyVE5pTUpXOl2zVQuk=s68-c-k-c0x00ffffff-no-rj

320 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

16 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

14 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

33 ms

id

id

40 ms

Create

Create

114 ms

XMLDirector

XMLDirector

226 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

21 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

63 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

69 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

77 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

91 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

91 ms

_buildManifest.js

_buildManifest.js

90 ms

_ssgManifest.js

_ssgManifest.js

100 ms

matomo.php

matomo.php

698 ms

GenerateIT

GenerateIT

50 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

12 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

11 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

4 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

8 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

16 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

16 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

7 ms

en-us.js

en-us.js

202 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

High

Page has valid source maps

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: