Express.live Site Title

Business AM - Think Forward

Express.live Meta Description

Business AM is jouw leidraad doorheen een steeds veranderende wereld. Ben jij mee? Hol niet achter de feiten aan dankzij Business AM.

Express.live Test Results

Express.live Mobile Performance: 27/100
Quick overview:
Time to Interactive
49.3 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.
Max Potential First Input Delay
1,450 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.
First Meaningful Paint
4.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Diagnostics
Collection of useful page vitals.
Final Screenshot
The last screenshot captured of the pageload.

1149132749518

Server Backend Latencies
560 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Network Round Trip Times
140 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Script Treemap Data
Used for treemap app
Network Requests
Lists the network requests that were made during page load.
Metrics
Collects all available metrics.

Express.live Mobile SEO: 84/100
Quick overview:
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 how to make pages mobile-friendly.
Tap targets are not sized appropriately
84% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Express.live Mobile Best Practices: 41/100
Quick overview:
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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
General
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more about unload event listeners
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
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
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Express.live Mobile PWA: 88/100
Quick overview:
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons.
Express.live Mobile Accessibility: 79/100
Quick overview:
Touch targets have sufficient size and 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.
Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
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.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Similar sites
Similar tests
www.express.com
www.express.net
www.express.org
www.express.info
www.express.biz
www.express.us
www.express.mobi
www.xpress.live
www.express.live
www.wxpress.live
www.ewxpress.live
www.wexpress.live
www.sxpress.live
www.esxpress.live
www.dxpress.live
www.edxpress.live
www.dexpress.live
www.rxpress.live
www.erxpress.live
www.rexpress.live
www.epress.live
www.ezpress.live
www.exzpress.live
www.ezxpress.live
www.espress.live
www.exspress.live
www.edpress.live
www.exdpress.live
www.ecpress.live
www.excpress.live
www.ecxpress.live
www.exress.live
www.exoress.live
www.exporess.live
www.exopress.live
www.exlress.live
www.explress.live
www.exlpress.live
www.expess.live
www.expeess.live
www.expreess.live
www.experess.live
www.expdess.live
www.exprdess.live
www.expdress.live
www.expfess.live
www.exprfess.live
www.expfress.live
www.exptess.live
www.exprtess.live
www.exptress.live
www.exprss.live
www.exprwss.live
www.exprewss.live
www.exprwess.live
www.exprsss.live
www.expresss.live
www.exprsess.live
www.exprdss.live
www.expredss.live
www.exprrss.live
www.exprerss.live
www.exprress.live
www.expres.live
www.exprews.live
www.expresws.live
www.exprees.live
www.expreses.live
www.expreds.live
www.expresds.live
www.exprezs.live
www.expreszs.live
www.exprezss.live
www.exprexs.live
www.expresxs.live
www.exprexss.live
www.expreas.live
www.expresas.live
www.expreass.live
www.expresw.live
www.expressw.live
www.exprese.live
www.expresse.live
www.expresd.live
www.expressd.live
www.expresz.live
www.expressz.live
www.expresx.live
www.expressx.live
www.expresa.live
www.expressa.live
Last Tested: