Apeka.nl Site Title

Mijn FORUM

Apeka.nl Test Results

Apeka.nl Mobile Performance: 97/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Eliminate render-blocking resources
Potential savings of 1,000 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.
Serve static assets with an efficient cache policy
11 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Apeka.nl Mobile SEO: 91/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.

Apeka.nl Mobile Best Practices: 66/100
Quick overview:
Trust and Safety
Does not redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Does not use HTTPS
13 insecure requests 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.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document contains a `doctype` that triggers `limited-quirks-mode`
User Experience
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Apeka.nl 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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Contrast
These are opportunities to improve the legibility of your content.
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.
`<td>` elements in a large `<table>` do not have table headers.
Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
Tables do not use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `colspan]` attribute may improve the experience for screen reader users. [Learn more about captions.
Similar sites
Similar tests
www.apeka.com
www.apeka.net
www.apeka.org
www.apeka.info
www.apeka.biz
www.apeka.us
www.apeka.mobi
www.peka.nl
www.apeka.nl
www.qpeka.nl
www.aqpeka.nl
www.qapeka.nl
www.wpeka.nl
www.awpeka.nl
www.wapeka.nl
www.speka.nl
www.aspeka.nl
www.sapeka.nl
www.zpeka.nl
www.azpeka.nl
www.zapeka.nl
www.aeka.nl
www.aoeka.nl
www.apoeka.nl
www.aopeka.nl
www.aleka.nl
www.apleka.nl
www.alpeka.nl
www.apka.nl
www.apwka.nl
www.apewka.nl
www.apweka.nl
www.apska.nl
www.apeska.nl
www.apseka.nl
www.apdka.nl
www.apedka.nl
www.apdeka.nl
www.aprka.nl
www.aperka.nl
www.apreka.nl
www.apea.nl
www.apeja.nl
www.apekja.nl
www.apejka.nl
www.apeia.nl
www.apekia.nl
www.apeika.nl
www.apema.nl
www.apekma.nl
www.apemka.nl
www.apela.nl
www.apekla.nl
www.apelka.nl
www.apeoa.nl
www.apekoa.nl
www.apeoka.nl
www.apek.nl
www.apekq.nl
www.apekaq.nl
www.apekqa.nl
www.apekw.nl
www.apekaw.nl
www.apekwa.nl
www.apeks.nl
www.apekas.nl
www.apeksa.nl
www.apekz.nl
www.apekaz.nl
www.apekza.nl
Last Tested: