Tools & Wizards About Us
wundergraph.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

wundergraph.com

WunderGraph Cosmo: The Open-Source API Federation Platform - WunderGraph

Page Load Speed

1.8 sec in total

First Response

37 ms

Resources Loaded

745 ms

Page Rendered

1.1 sec

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 37 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

wundergraph.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

wundergraph.com

37 ms

wundergraph.com

89 ms

l.js

103 ms

sdk.js

350 ms

8f48a7146d300e81.css

30 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 237.4 kB (38%)

Content Size

620.8 kB

After Optimization

383.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 180.7 kB

  • Original 232.8 kB
  • After minification 232.2 kB
  • After compression 52.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 180.7 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 2.4 kB

  • Original 195.6 kB
  • After minification 193.2 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 19.9 kB

  • Original 143.6 kB
  • After minification 143.6 kB
  • After compression 123.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 19.9 kB or 14% of the original size.

CSS Optimization

-71%

Potential reduce by 34.5 kB

  • Original 48.8 kB
  • After minification 17.3 kB
  • After compression 14.3 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 34.5 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (33%)

Requests Now

60

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 60 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 21 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

wundergraph.com

wundergraph.com

37 ms

wundergraph.com

wundergraph.com

89 ms

l.js

l.js

103 ms

sdk.js

sdk.js

350 ms

8f48a7146d300e81.css

8f48a7146d300e81.css

30 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

126 ms

webpack-31777c33366b8d89.js

webpack-31777c33366b8d89.js

100 ms

framework-38e28be3ecb6834a.js

framework-38e28be3ecb6834a.js

148 ms

main-25bfe789bbcf7e71.js

main-25bfe789bbcf7e71.js

124 ms

_app-0d9289f1b3246de6.js

_app-0d9289f1b3246de6.js

157 ms

163208ec-2e7754baf0ec213c.js

163208ec-2e7754baf0ec213c.js

123 ms

3303f019-0fb471e357b6f777.js

3303f019-0fb471e357b6f777.js

124 ms

5863-92d6ef7ac8cb38d1.js

5863-92d6ef7ac8cb38d1.js

165 ms

2475-a80b335785a4f950.js

2475-a80b335785a4f950.js

164 ms

1634-9f1c2d1a20ee2920.js

1634-9f1c2d1a20ee2920.js

163 ms

3528-f474c2818fe6e4a2.js

3528-f474c2818fe6e4a2.js

166 ms

2479-096eaba771c04163.js

2479-096eaba771c04163.js

163 ms

4643-5fb0d6085fa8e05a.js

4643-5fb0d6085fa8e05a.js

193 ms

4680-dd810714728dd10f.js

4680-dd810714728dd10f.js

192 ms

index-5f4afe409e734787.js

index-5f4afe409e734787.js

193 ms

_buildManifest.js

_buildManifest.js

193 ms

_ssgManifest.js

_ssgManifest.js

192 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

159 ms

cosmo.svg

cosmo.svg

161 ms

badge

badge

476 ms

badge

badge

547 ms

tailor.svg

tailor.svg

261 ms

image

image

277 ms

redventures.svg

redventures.svg

268 ms

equinix.svg

equinix.svg

264 ms

crypto.svg

crypto.svg

270 ms

ontheBeach.svg

ontheBeach.svg

262 ms

eog.svg

eog.svg

271 ms

fanduel.svg

fanduel.svg

270 ms

innio.svg

innio.svg

272 ms

saks.svg

saks.svg

273 ms

khealth.svg

khealth.svg

275 ms

monkeyfactory.svg

monkeyfactory.svg

277 ms

image

image

339 ms

image

image

279 ms

travelpassgroup.svg

travelpassgroup.svg

281 ms

soundtrack.svg

soundtrack.svg

285 ms

cbn.svg

cbn.svg

294 ms

bonprix.svg

bonprix.svg

279 ms

image

image

348 ms

procore.svg

procore.svg

280 ms

client.js

client.js

84 ms

client_default.css

client_default.css

104 ms

acoustic.svg

acoustic.svg

257 ms

superbet.svg

superbet.svg

259 ms

roche.svg

roche.svg

235 ms

soundcloud.svg

soundcloud.svg

241 ms

image

image

306 ms

image

image

276 ms

image

image

409 ms

image

image

293 ms

image

image

323 ms

image

image

356 ms

image

image

342 ms

image

image

311 ms

soc2.png

soc2.png

308 ms

status_page_v2-2edc7e5acacc6e88031b40bf05f68e80fc6a1d3dcaf8f0b55f173925d2e8e844.css

status_page_v2-2edc7e5acacc6e88031b40bf05f68e80fc6a1d3dcaf8f0b55f173925d2e8e844.css

42 ms

Accessibility Review

wundergraph.com accessibility score

85

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: