C-lab.de Site Title

C-Lab  -  Startseite (Universität Paderborn)

C-lab.de Test Results

C-lab.de Mobile Performance: 55/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.
Avoid multiple page redirects
Potential savings of 1,420 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused CSS
Potential savings of 82 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Largest Contentful Paint element
6,950 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Minimize main-thread work
2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Avoid large layout shifts
3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Reduce initial server response time
Root document took 620 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Serve images in next-gen formats
Potential savings of 1,775 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Reduce unused JavaScript
Potential savings of 165 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Eliminate render-blocking resources
Potential savings of 1,170 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Remove duplicate modules in JavaScript bundles
Potential savings of 29 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Efficiently encode images
Potential savings of 136 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Avoid an excessive DOM size
953 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Properly size images
Potential savings of 2,789 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Enable text compression
Potential savings of 41 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Avoid enormous network payloads
Total size was 3,633 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Serve static assets with an efficient cache policy
39 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Max Potential First Input Delay
280 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Time to Interactive
6.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
First Meaningful Paint
3.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

C-lab.de Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

C-lab.de Mobile Best Practices: 79/100
Quick overview:
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
C-lab.de Mobile Accessibility: 89/100
Quick overview:
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.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Similar tests
www.c-lab.com
www.c-lab.net
www.c-lab.org
www.c-lab.info
www.c-lab.biz
www.c-lab.us
www.c-lab.mobi
www.-lab.de
www.c-lab.de
www.x-lab.de
www.cx-lab.de
www.xc-lab.de
www.d-lab.de
www.cd-lab.de
www.dc-lab.de
www.f-lab.de
www.cf-lab.de
www.fc-lab.de
www.v-lab.de
www.cv-lab.de
www.vc-lab.de
www.clab.de
www.c-ab.de
www.c-pab.de
www.c-lpab.de
www.c-plab.de
www.c-oab.de
www.c-loab.de
www.c-olab.de
www.c-kab.de
www.c-lkab.de
www.c-klab.de
www.c-lb.de
www.c-lqb.de
www.c-laqb.de
www.c-lqab.de
www.c-lwb.de
www.c-lawb.de
www.c-lwab.de
www.c-lsb.de
www.c-lasb.de
www.c-lsab.de
www.c-lzb.de
www.c-lazb.de
www.c-lzab.de
www.c-la.de
www.c-lav.de
www.c-labv.de
www.c-lavb.de
www.c-lag.de
www.c-labg.de
www.c-lagb.de
www.c-lah.de
www.c-labh.de
www.c-lahb.de
www.c-lan.de
www.c-labn.de
www.c-lanb.de
Last Tested: