Antler.co Site Title

Global early-stage VC enabling and investing in the world's most exceptional people | Antler

Antler.co Meta Description

Build your next company with Antler, a global early-stage VC enabling and investing in the world's most exceptional people building the defining companies of tomorrow.

Antler.co Test Results

Antler.co Mobile Performance: 35/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript. Potential savings of 303 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Avoid multiple page redirects. Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Eliminate render-blocking resources. Potential savings of 600 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.
Minify JavaScript. Potential savings of 40 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Serve images in next-gen formats. Potential savings of 52 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.
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
5.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Serve static assets with an efficient cache policy
7 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Reduce JavaScript execution time
2.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Keep request counts low and transfer sizes small
51 requests • 1,110 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
1 chain 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.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid long main-thread tasks
16 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Antler.co Mobile SEO: 99/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 more.
Tap targets are not sized appropriately
96% 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.

Antler.co Mobile Best Practices: 92/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 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.
Antler.co Mobile Progressive Web App: 64/100
Quick overview:
Installable
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. 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.
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.
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. The start_url did respond, but not via a service worker.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Antler.co Mobile Accessibility: 80/100
Quick overview:
Tables and lists
These are opportunities to 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.
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on 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.
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 sites
Similar tests
www.antler.com
www.antler.net
www.antler.org
www.antler.info
www.antler.biz
www.antler.us
www.antler.mobi
www.ntler.co
www.antler.co
www.qntler.co
www.aqntler.co
www.qantler.co
www.wntler.co
www.awntler.co
www.wantler.co
www.sntler.co
www.asntler.co
www.santler.co
www.zntler.co
www.azntler.co
www.zantler.co
www.atler.co
www.abtler.co
www.anbtler.co
www.abntler.co
www.ahtler.co
www.anhtler.co
www.ahntler.co
www.ajtler.co
www.anjtler.co
www.ajntler.co
www.amtler.co
www.anmtler.co
www.amntler.co
www.anler.co
www.anrler.co
www.antrler.co
www.anrtler.co
www.anfler.co
www.antfler.co
www.anftler.co
www.angler.co
www.antgler.co
www.angtler.co
www.anyler.co
www.antyler.co
www.anytler.co
www.anter.co
www.antper.co
www.antlper.co
www.antpler.co
www.antoer.co
www.antloer.co
www.antoler.co
www.antker.co
www.antlker.co
www.antkler.co
www.antlr.co
www.antlwr.co
www.antlewr.co
www.antlwer.co
www.antlsr.co
www.antlesr.co
www.antlser.co
www.antldr.co
www.antledr.co
www.antlder.co
www.antlrr.co
www.antlerr.co
www.antlrer.co
www.antle.co
www.antlee.co
www.antlere.co
www.antleer.co
www.antled.co
www.antlerd.co
www.antlef.co
www.antlerf.co
www.antlefr.co
www.antlet.co
www.antlert.co
www.antletr.co
Last Tested: