Tools & Wizards About Us
xprag.de screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    37% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

xprag.de

| New Pragmatic Theories based on Experimental Evidence (SPP 1727)

Page Load Speed

6.1 sec in total

First Response

872 ms

Resources Loaded

4.9 sec

Page Rendered

306 ms

xprag.de screenshot

About Website

Visit xprag.de now to see the best up-to-date Xprag content and also check out these interesting facts you probably never knew about xprag.de

The overall goal of XPRAG.de was to develop a precise pragmatic theory that is informed by evidence using experimental methods. The program was addressed at researchers in linguistics, psychology, neu...

Visit xprag.de

Key Findings

We analyzed Xprag.de page load time and found that the first response time was 872 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

xprag.de performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value2,150 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

www.xprag.de

872 ms

wp-emoji-release.min.js

146 ms

style.min.css

488 ms

css2

104 ms

jquery-ui.css

392 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 59% of them (34 requests) were addressed to the original Xprag.de, 17% (10 requests) were made to Fonts.gstatic.com and 14% (8 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Xprag.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 928.7 kB (73%)

Content Size

1.3 MB

After Optimization

342.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xprag.de 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. 80% 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. CSS take 648.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 26.2 kB

  • Original 34.4 kB
  • After minification 33.3 kB
  • After compression 8.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 26.2 kB or 76% of the original size.

Image Optimization

-20%

Potential reduce by 14.2 kB

  • Original 72.2 kB
  • After minification 58.1 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, Xprag needs image optimization as it can save up to 14.2 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 354.3 kB

  • Original 516.1 kB
  • After minification 507.6 kB
  • After compression 161.8 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 354.3 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 534.0 kB

  • Original 648.9 kB
  • After minification 612.5 kB
  • After compression 114.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. Xprag.de needs all CSS files to be minified and compressed as it can save up to 534.0 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

47

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.xprag.de

www.xprag.de

872 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

146 ms

style.min.css

style.min.css

488 ms

css2

css2

104 ms

jquery-ui.css

jquery-ui.css

392 ms

jquery.remodal.css

jquery.remodal.css

233 ms

unite-gallery.css

unite-gallery.css

348 ms

skin-right-no-thumb.css

skin-right-no-thumb.css

223 ms

skin-right-thumb.css

skin-right-thumb.css

226 ms

skin-right-title-only.css

skin-right-title-only.css

334 ms

css

css

70 ms

genericons.css

genericons.css

464 ms

style.css

style.css

348 ms

blocks.css

blocks.css

469 ms

zotpress.shortcode.min.css

zotpress.shortcode.min.css

457 ms

jquery.min.js

jquery.min.js

665 ms

jquery-migrate.min.js

jquery-migrate.min.js

452 ms

accordion.js

accordion.js

577 ms

unitegallery.min.js

unitegallery.min.js

1006 ms

ug-theme-video.js

ug-theme-video.js

552 ms

ug-theme-tilesgrid.js

ug-theme-tilesgrid.js

559 ms

core.min.js

core.min.js

585 ms

accordion.min.js

accordion.min.js

676 ms

tooltip.min.js

tooltip.min.js

677 ms

jquery.remodal.min.js

jquery.remodal.min.js

673 ms

photowall.js

photowall.js

689 ms

imagesloaded.min.js

imagesloaded.min.js

742 ms

masonry.min.js

masonry.min.js

798 ms

jquery.masonry.min.js

jquery.masonry.min.js

782 ms

functions.js

functions.js

787 ms

css

css

15 ms

style.css

style.css

598 ms

cropped-Banner7_final8X2.png

cropped-Banner7_final8X2.png

222 ms

logo_match_banner1.png

logo_match_banner1.png

1452 ms

search-icon.png

search-icon.png

222 ms

dfg_logo_schriftzug_schwarz_foerderung_en-300x97.jpg

dfg_logo_schriftzug_schwarz_foerderung_en-300x97.jpg

1529 ms

ZAS-Web-d-300x99.png

ZAS-Web-d-300x99.png

1529 ms

player_api

player_api

239 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYi1UA.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYi1UA.ttf

204 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4i1UA.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4i1UA.ttf

234 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZMkidi18E.ttf

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZMkidi18E.ttf

265 ms

6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7psDc.ttf

6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7psDc.ttf

263 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclSdi18E.ttf

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclSdi18E.ttf

265 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdr.ttf

263 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf

242 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf

257 ms

www-widgetapi.js

www-widgetapi.js

88 ms

ebiKFO-8Qv0

ebiKFO-8Qv0

74 ms

www-player.css

www-player.css

27 ms

www-embed-player.js

www-embed-player.js

175 ms

base.js

base.js

290 ms

fetch-polyfill.js

fetch-polyfill.js

172 ms

ad_status.js

ad_status.js

601 ms

Y-zeT9jJ33tCNYTX0Kw8-3I-ogsAM9wZgys9W8554e8.js

Y-zeT9jJ33tCNYTX0Kw8-3I-ogsAM9wZgys9W8554e8.js

505 ms

embed.js

embed.js

94 ms

id

id

73 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

112 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

110 ms

Accessibility Review

xprag.de accessibility score

93

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

xprag.de best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

xprag.de SEO score

100

Search Engine Optimization Advices

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

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 Xprag.de 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 Xprag.de 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

xprag.de

Open Graph data is detected on the main page of Xprag. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: