Tools & Wizards About Us
wundergraph.com screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

wundergraph.com

WunderGraph Cosmo: The Open-Source GraphQL Federation Solution - WunderGraph

Page Load Speed

2.3 sec in total

First Response

152 ms

Resources Loaded

1.2 sec

Page Rendered

947 ms

wundergraph.com screenshot

About Website

Click here to check amazing Wunder Graph content. Otherwise, check out these important facts you probably never knew about wundergraph.com

Full lifecycle API Management for (Federated) GraphQL. Schema registry, composition checks, analytics, metrics, tracing and routing. Deploy 100% on-prem or use our Managed Service. Apache 2.0 licensed...

Visit wundergraph.com

Key Findings

We analyzed Wundergraph.com page load time and found that the first response time was 152 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

wundergraph.com performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

wundergraph.com

152 ms

l.js

126 ms

sdk.js

172 ms

fa8f989898913436.css

48 ms

polyfills-c67a75d1b6f99dc8.js

128 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 80% of them (36 requests) were addressed to the original Wundergraph.com, 7% (3 requests) were made to Client.crisp.chat and 7% (3 requests) were made to Status.wundergraph.com. The less responsive or slowest element that took the longest time to load (477 ms) relates to the external source Status.wundergraph.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 364.3 kB (53%)

Content Size

684.1 kB

After Optimization

319.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wundergraph.com main page is 684.1 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. 45% of websites need less resources to load. HTML takes 236.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 178.1 kB

  • Original 236.1 kB
  • After minification 235.7 kB
  • After compression 58.0 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 178.1 kB or 75% of the original size.

Image Optimization

-8%

Potential reduce by 3.9 kB

  • Original 51.0 kB
  • After minification 47.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. Wunder Graph images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 21.9 kB

  • Original 161.0 kB
  • After minification 161.0 kB
  • After compression 139.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 21.9 kB or 14% of the original size.

CSS Optimization

-68%

Potential reduce by 160.5 kB

  • Original 236.0 kB
  • After minification 206.0 kB
  • After compression 75.6 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. Wundergraph.com needs all CSS files to be minified and compressed as it can save up to 160.5 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (39%)

Requests Now

44

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wundergraph.com

wundergraph.com

152 ms

l.js

l.js

126 ms

sdk.js

sdk.js

172 ms

fa8f989898913436.css

fa8f989898913436.css

48 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

128 ms

webpack-ee2ab5004739d903.js

webpack-ee2ab5004739d903.js

123 ms

framework-38e28be3ecb6834a.js

framework-38e28be3ecb6834a.js

41 ms

main-2160b1938b46bd22.js

main-2160b1938b46bd22.js

33 ms

_app-2f99131d27a0968b.js

_app-2f99131d27a0968b.js

122 ms

163208ec-2e7754baf0ec213c.js

163208ec-2e7754baf0ec213c.js

166 ms

3303f019-2733a57fc9ecce45.js

3303f019-2733a57fc9ecce45.js

172 ms

625-714ee53dd4787e92.js

625-714ee53dd4787e92.js

124 ms

2200-eae9f0245688f6b5.js

2200-eae9f0245688f6b5.js

124 ms

3528-f474c2818fe6e4a2.js

3528-f474c2818fe6e4a2.js

124 ms

1582-78008db940b7a494.js

1582-78008db940b7a494.js

166 ms

index-7042dbf4b3785dfc.js

index-7042dbf4b3785dfc.js

169 ms

_buildManifest.js

_buildManifest.js

166 ms

_ssgManifest.js

_ssgManifest.js

167 ms

v84a3a4012de94ce1a686ba8c167c359c1696973893317

v84a3a4012de94ce1a686ba8c167c359c1696973893317

166 ms

cosmo.svg

cosmo.svg

274 ms

badge

badge

431 ms

badge

badge

429 ms

mryum.svg

mryum.svg

90 ms

crypto.svg

crypto.svg

95 ms

sap.svg

sap.svg

93 ms

tripadvisor.svg

tripadvisor.svg

95 ms

tailor.svg

tailor.svg

91 ms

mongodb.svg

mongodb.svg

97 ms

auth0.svg

auth0.svg

99 ms

oracle.svg

oracle.svg

99 ms

fauna-light.svg

fauna-light.svg

100 ms

coinweb.svg

coinweb.svg

239 ms

artnet.svg

artnet.svg

101 ms

image

image

249 ms

monkeyfactory.svg

monkeyfactory.svg

102 ms

innio.svg

innio.svg

110 ms

travelpassgroup.svg

travelpassgroup.svg

112 ms

sharpapp.svg

sharpapp.svg

110 ms

soundtrack.svg

soundtrack.svg

199 ms

inks.svg

inks.svg

134 ms

image

image

297 ms

soc2.png

soc2.png

236 ms

client.js

client.js

32 ms

client_legacy.css

client_legacy.css

120 ms

status_page_v2-bfecab43.css

status_page_v2-bfecab43.css

477 ms

Accessibility Review

wundergraph.com accessibility score

86

Accessibility Issues

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

Buttons do not have an accessible name

High

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

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

Best Practices

wundergraph.com 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

Missing source maps for large first-party JavaScript

SEO Factors

wundergraph.com SEO score

90

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 Wundergraph.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 Wundergraph.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.

Social Sharing Optimization

wundergraph.com

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