Apekade.sg Site Title

Home Page - Ape Kade

Apekade.sg Test Results

Apekade.sg Mobile Performance: 12/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats. Potential savings of 1,918 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Properly size images. Potential savings of 386 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Efficiently encode images. Potential savings of 144 KiB
Optimized images load faster and consume less cellular data. Learn more.
Reduce initial server response time. Root document took 700 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Remove unused JavaScript. Potential savings of 108 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Eliminate render-blocking resources. Potential savings of 300 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Minimize main-thread work
7.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
5.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid an excessive DOM size
1,180 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Avoid enormous network payloads
Total size was 2,755 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
15 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Avoid long main-thread tasks
19 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Keep request counts low and transfer sizes small
59 requests • 2,755 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More

Apekade.sg 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.
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.
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.
Tap targets are not sized appropriately
90% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Apekade.sg Mobile Best Practices: 71/100
Quick overview:
General
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
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 servedover 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.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Apekade.sg Mobile Progressive Web App: 89/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 more.
Installable
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 servedover 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.
Apekade.sg Mobile Accessibility: 67/100
Quick overview:
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>` or `<ol>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
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.
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.
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.
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 more.
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.
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 more.
Similar tests
www.apekade.com
www.apekade.net
www.apekade.org
www.apekade.info
www.apekade.biz
www.apekade.us
www.apekade.mobi
www.pekade.sg
www.apekade.sg
www.qpekade.sg
www.aqpekade.sg
www.qapekade.sg
www.wpekade.sg
www.awpekade.sg
www.wapekade.sg
www.spekade.sg
www.aspekade.sg
www.sapekade.sg
www.zpekade.sg
www.azpekade.sg
www.zapekade.sg
www.aekade.sg
www.aoekade.sg
www.apoekade.sg
www.aopekade.sg
www.alekade.sg
www.aplekade.sg
www.alpekade.sg
www.apkade.sg
www.apwkade.sg
www.apewkade.sg
www.apwekade.sg
www.apskade.sg
www.apeskade.sg
www.apsekade.sg
www.apdkade.sg
www.apedkade.sg
www.apdekade.sg
www.aprkade.sg
www.aperkade.sg
www.aprekade.sg
www.apeade.sg
www.apejade.sg
www.apekjade.sg
www.apejkade.sg
www.apeiade.sg
www.apekiade.sg
www.apeikade.sg
www.apemade.sg
www.apekmade.sg
www.apemkade.sg
www.apelade.sg
www.apeklade.sg
www.apelkade.sg
www.apeoade.sg
www.apekoade.sg
www.apeokade.sg
www.apekde.sg
www.apekqde.sg
www.apekaqde.sg
www.apekqade.sg
www.apekwde.sg
www.apekawde.sg
www.apekwade.sg
www.apeksde.sg
www.apekasde.sg
www.apeksade.sg
www.apekzde.sg
www.apekazde.sg
www.apekzade.sg
www.apekae.sg
www.apekaxe.sg
www.apekadxe.sg
www.apekaxde.sg
www.apekase.sg
www.apekadse.sg
www.apekaee.sg
www.apekadee.sg
www.apekaede.sg
www.apekare.sg
www.apekadre.sg
www.apekarde.sg
www.apekafe.sg
www.apekadfe.sg
www.apekafde.sg
www.apekace.sg
www.apekadce.sg
www.apekacde.sg
www.apekad.sg
www.apekadw.sg
www.apekadew.sg
www.apekadwe.sg
www.apekads.sg
www.apekades.sg
www.apekadd.sg
www.apekaded.sg
www.apekadde.sg
www.apekadr.sg
www.apekader.sg
Last Tested: