Flokk.com Site Title

Flokk | Home

Flokk.com Meta Description

Flokk provides a wide range of furniture and acoustic solutions. With a shared belief in human-centred and sustainable design, each of our brands has its own unique identity, and their own stories to tell.

Flokk.com Test Results

Flokk.com Mobile Performance: 31/100
Quick overview:
Time to Interactive
21.4 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.
First Meaningful Paint
7.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Max Potential First Input Delay
430 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.

Flokk.com Mobile SEO: 79/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
7 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
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

Flokk.com Mobile Best Practices: 81/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 about source maps.
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.
Flokk.com Mobile PWA: 38/100
Quick overview:
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.
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. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens. Failures: No manifest was fetched.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Flokk.com Mobile Accessibility: 62/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.
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.
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 how to make buttons more accessible.
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.
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.
Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Tables and lists
These are opportunities 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 about proper list structure.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
`[id]` attributes on active, focusable elements are not unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn how to fix duplicate `id`s.
Similar sites
Similar tests
www.flokk.com
www.flokk.net
www.flokk.org
www.flokk.info
www.flokk.biz
www.flokk.us
www.flokk.mobi
www.lokk.com
www.flokk.com
www.clokk.com
www.fclokk.com
www.cflokk.com
www.dlokk.com
www.fdlokk.com
www.dflokk.com
www.rlokk.com
www.frlokk.com
www.rflokk.com
www.tlokk.com
www.ftlokk.com
www.tflokk.com
www.glokk.com
www.fglokk.com
www.gflokk.com
www.vlokk.com
www.fvlokk.com
www.vflokk.com
www.fokk.com
www.fpokk.com
www.flpokk.com
www.fplokk.com
www.fookk.com
www.flookk.com
www.folokk.com
www.fkokk.com
www.flkokk.com
www.fklokk.com
www.flkk.com
www.flikk.com
www.floikk.com
www.fliokk.com
www.flkkk.com
www.flokkk.com
www.fllkk.com
www.flolkk.com
www.fllokk.com
www.flpkk.com
www.flopkk.com
www.flok.com
www.flojk.com
www.flokjk.com
www.flojkk.com
www.floik.com
www.flokik.com
www.flomk.com
www.flokmk.com
www.flomkk.com
www.flolk.com
www.floklk.com
www.flook.com
www.flokok.com
www.flokj.com
www.flokkj.com
www.floki.com
www.flokki.com
www.flokm.com
www.flokkm.com
www.flokl.com
www.flokkl.com
www.floko.com
www.flokko.com
www.flokk.con
Last Tested: