Kenp.io Site Title

About | Ken Pillonel

Kenp.io Meta Description

I'm currently doing a Master's degree in Robotics at the Swiss Federal Institute of Technology, EPFL. Robotics is a very interesting field as it requires good knowledge of both the hardware side of a project (Electrical, Mechanical, Material engineering) and also the Software development side. To improve on the latter, I'm also doing a Minor in Data Science at EPFL. In my spare time I like to tinker with 3D printing and IoT projects. I also work as an engineering consultant part time. For fun, I like to explore new countries and I don't hesitate to pack my backpack for a quick adventure when I have the opportunity to do so.

Kenp.io Test Results

Kenp.io Mobile Performance: 56/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Minimize main-thread work
2.0 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
Eliminate render-blocking resources
Potential savings of 730 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.
Largest Contentful Paint element
13,400 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce JavaScript execution time
1.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 reduce Javascript execution time.
Avoid large layout shifts
2 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 unused JavaScript
Potential savings of 197 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.
Serve images in next-gen formats
Potential savings of 2,220 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.
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
Avoid enormous network payloads
Total size was 3,667 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Defer offscreen images
Potential savings of 1,885 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Efficiently encode images
Potential savings of 1,495 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Serve static assets with an efficient cache policy
4 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
530 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
14.7 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.

Kenp.io Mobile SEO: 100/100
Quick overview:

Kenp.io 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.
Kenp.io Mobile Accessibility: 78/100
Quick overview:
Contrast
These are opportunities to improve the legibility of your content.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
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.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar sites
Similar tests
www.kenp.com
www.kenp.net
www.kenp.org
www.kenp.info
www.kenp.biz
www.kenp.us
www.kenp.mobi
www.enp.io
www.kenp.io
www.jenp.io
www.kjenp.io
www.jkenp.io
www.ienp.io
www.kienp.io
www.ikenp.io
www.menp.io
www.kmenp.io
www.mkenp.io
www.lenp.io
www.klenp.io
www.lkenp.io
www.oenp.io
www.koenp.io
www.okenp.io
www.knp.io
www.kwnp.io
www.kewnp.io
www.kwenp.io
www.ksnp.io
www.kesnp.io
www.ksenp.io
www.kdnp.io
www.kednp.io
www.kdenp.io
www.krnp.io
www.kernp.io
www.krenp.io
www.kep.io
www.kebp.io
www.kenbp.io
www.kebnp.io
www.kehp.io
www.kenhp.io
www.kehnp.io
www.kejp.io
www.kenjp.io
www.kejnp.io
www.kemp.io
www.kenmp.io
www.kemnp.io
www.ken.io
www.keno.io
www.kenpo.io
www.kenop.io
www.kenl.io
www.kenpl.io
www.kenlp.io
Last Tested: