Florr - Florr.io

Overview

Snoop Summary for florr.io

This is a free and comprehensive report about florr.io. Our records indicate that florr.io is privately registered by Cloudflare, Inc.. Florr.io has the potential to be earning an estimated $5 USD per day from advertising revenue. If florr.io was to be sold it would possibly be worth $3,418 USD (based on the daily revenue potential of the website over a 24 month period). Florr.io receives an estimated 1,638 unique visitors every day - a large amount of traffic! This report was last updated 22nd February, 2024.

About florr.io

Site Preview:
Title:	florr.io
Description:	Battle enemies and seek the rarest petals to add to your collection
Keywords and Tags:	games
Related Terms:	dominance
Fav Icon:
Age:	Over 3 years old
Domain Created:	1st June, 2020
Domain Updated:	12th August, 2023
Domain Expires:	1st June, 2025

Review

Snoop Score

2/5

Valuation

$3,418 USD

Note: All valuation figures are estimates.

Popularity

Modest

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	480,599
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority:	0
Moz Page Authority:	0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors:	1,638
Monthly Visitors:	49,864
Yearly Visitors:	597,969

Note: All visitors figures are estimates.

Visitors By Country

Revenue

Daily Revenue:	$5 USD
Monthly Revenue:	$142 USD
Yearly Revenue:	$1,704 USD

Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	florr.io	8
Domain Name:	florr	5
Extension (TLD):	io	2

Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

PWA

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: https://florr.io/

Updated: 30th March, 2022

1.62 seconds

First Contentful Paint (FCP)

81%

13%

6%

0.01 seconds

First Input Delay (FID)

97%

2%

1%

Simulate loading on desktop

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for florr.io. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.

Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Largest Contentful Paint — 0.8 s
The timing of the largest text or image that is painted.

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://florr.io/	http/1.1	0	53.139000199735	704	0	301	text/plain
https://florr.io/	h2	53.532999940217	398.4640003182	2518	4429	200	text/html	Document
https://fonts.googleapis.com/css?family=Ubuntu:700	h2	409.91500020027	421.35199997574	1266	1728	200	text/css	Stylesheet
https://static.florr.io/be956309c38b570246a584a78a10cd5e7506f6d7/client.js	h2	424.84200000763	524.84100032598	38119	112596	200	text/plain	Script
https://fonts.gstatic.com/s/ubuntu/v19/4iCv6KVjbNBYlgoCxCvjsGyNPYZvgw.woff2	h2	425.92400033027	429.50400011614	15856	14928	200	font/woff2	Font
https://static.florr.io/be956309c38b570246a584a78a10cd5e7506f6d7/client.wasm	h2	543.91800006852	709.57300020382	514364	1795019	200	application/wasm	Fetch
https://api.n.m28.io/endpoint/florrio/findEach/	h2	1082.4589999393	1296.1290003732	927	217	200	application/json	XHR
https://api.n.m28.io/endpoint/latency/findEach/	h2	1298.4510003589	1544.3710000254	1237	1327	200	application/json	XHR

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
438.976	6.669
463.999	6.356
572.144	9.679
747.662	8.449
756.299	319.416
1075.746	5.189
1083.184	15.89
1104.727	7.327
1118.702	8.075
1132.693	6.063
1144.071	6.322
1158.177	6.768
1174.878	9.467
1191.666	10.515
1208.212	8.342
1225.106	7.39
1241.484	7.092
1258.139	7.234
1274.861	7.1
1291.783	6.605
1308.185	6.839
1324.957	7.899
1341.484	11.195
1358.615	7.321
1374.788	7.337
1391.468	6.991
1408.165	7.448
1424.889	6.385
1441.542	7.679
1458.105	6.463
1474.793	8.243
1491.596	9.171
1511.41	11.092
1528.33	8.594
1542.12	9.265
1558.572	13.261
1576.823	12.537
1589.426	9.959
1599.492	15.546
1617.608	12.595
1634.43	13.424
1650.99	10.133
1665.38	10.234
1680.01	7.946
1692.342	6.707
1708.092	9.524
1724.789	6.531
1741.615	7.921
1758.17	7.594
1774.878	7.472
1791.443	6.716
1808.395	7.895
1825.329	11.652
1844.53	7.684
1858.111	6.774
1874.788	9.196
1891.446	6.692
1908.338	7.648
1924.796	7.891
1941.504	6.737
1958.512	7.121
1975.768	8.34
1991.41	6.532
2008.23	8.376
2024.785	8.852
2041.397	6.279
2058.113	8.335
2074.784	7.646
2092.563	8.941
2108.228	9.131
2124.759	7.136
2141.675	8.72
2158.179	13.376
2185.597	17.802
2207.152	10.509
2229.946	12.093
2251.013	15.716
2266.883	9.784
2281.009	10.994
2297.561	15.457
2319.853	9.894
2336.175	12.791
2349	10.953
2364.394	9.925
2378.867	9.522
2393.328	8.401
2408.51	12.374
2425.622	13.631
2441.74	7.564
2458.047	6.103
2474.74	6.101
2491.444	6.997
2508.37	6.978
2524.979	6.854
2541.416	6.182
2558.089	6.381
2574.833	7.013
2591.412	6.752
2608.309	6.058
2624.703	6.946
2641.721	6.629
2658.055	6.206
2674.786	8.788
2691.404	6.5
2708.125	6.34
2724.827	7.685
2741.582	7.5
2758.088	10.452
2775.007	6.147
2791.411	6.325
2808.081	6.501
2824.782	7.167
2841.422	7.421
2858.319	11.409
2874.783	6.431
2893.341	6.356
2908.057	6.392
2924.788	6.173
2941.375	6.861
2958.239	6.172
2974.728	6.19
2991.412	6.978
3008.421	6.499
3024.87	7.022
3041.411	7.735
3058.064	7.736
3074.823	6.507
3091.686	9.448
3108.846	7.526
3124.837	6.727
3141.378	6.696
3158.065	6.379
3174.761	7.769
3191.619	6.438
3208.103	7.765
3224.833	6.819
3241.39	7.754
3258.033	9.197
3274.756	11.183
3291.44	6.751
3308.117	6.046
3324.755	6.574
3341.408	8.732
3358.132	7.218
3374.831	9.304
3391.37	8.395
3408.046	9.897
3424.973	6.811
3441.531	8.409
3458.052	8.723
3474.829	8.393
3491.483	8.835
3508.13	8.423
3528.571	9.646
3546.821	9.759
3563.345	8.908
3578.697	9.492
3594.811	11.941
3614.628	7.801
3629.289	11.039
3646.462	8.385
3660.276	7.771
3676.19	8.829
3692.123	8.583
3708.596	12.209
3728.382	6.468
3742.152	7.073
3758.068	7.479
3774.833	7.395
3791.342	6.307
3808.663	6.486
3824.894	6.78
3841.485	10.477
3858.383	9.432
3875.337	9.005
3891.41	6.471
3908.142	7.413

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Florr.io should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Florr.io should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Florr.io should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Florr.io should consider minifying JS files.

Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Florr.io should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

Reduce unused JavaScript — Potential savings of 27 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
https://static.florr.io/be956309c38b570246a584a78a10cd5e7506f6d7/client.js	38119	27168

Show Details

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.

Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Initial server response time was short — Root document took 350 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.

URL	Time Spent (Ms)
https://florr.io/	345.925

Show Details

Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Florr.io should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
http://florr.io/	190
https://florr.io/	0

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Florr.io should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.

Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Avoids enormous network payloads — Total size was 562 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
https://static.florr.io/be956309c38b570246a584a78a10cd5e7506f6d7/client.wasm	514364
https://static.florr.io/be956309c38b570246a584a78a10cd5e7506f6d7/client.js	38119
https://fonts.gstatic.com/s/ubuntu/v19/4iCv6KVjbNBYlgoCxCvjsGyNPYZvgw.woff2	15856
https://florr.io/	2518
https://fonts.googleapis.com/css?family=Ubuntu:700	1266
https://api.n.m28.io/endpoint/latency/findEach/	1237
https://api.n.m28.io/endpoint/florrio/findEach/	927
http://florr.io/	704

Show Details

Uses efficient cache policy on static assets — 1 resource found
Florr.io can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

URL	Cache TTL (Ms)	Transfer Size (Bytes)
https://static.florr.io/be956309c38b570246a584a78a10cd5e7506f6d7/client.js	2678400000	38119

Show Details

Avoids an excessive DOM size — 22 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.

Statistic	Element	Value
Total DOM Elements		22
Maximum DOM Depth	Google Chrome	5
Maximum Child Elements	body	8

Show Details

Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Florr.io should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
https://florr.io/	1100.891	3.551	1.314
https://static.florr.io/be956309c38b570246a584a78a10cd5e7506f6d7/client.js	697.669	342.517	2.321

Show Details

Minimizes main-thread work — 1.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Category	Time Spent (Ms)
Rendering	1143.378
Script Evaluation	356.32
Other	305.599
Style & Layout	13.728
Garbage Collection	7.166
Script Parsing & Compilation	3.791
Parse HTML & CSS	1.917

Show Details

Keep request counts low and transfer sizes small — 8 requests • 562 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	8	574991
Other	4	517232
Script	1	38119
Font	1	15856
Document	1	2518
Stylesheet	1	1266
Image	0	0
Media	0	0
Third-party	4	19286

Show Details

Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Third-Party	Transfer Size (Bytes)	Main-Thread Blocking Time (Ms)
SHOW DETAILS	17122	0

Show Details

Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).

Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.

Element
Loading...

Show Details

Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.

Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.

Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

URL	Start Time (Ms)	Duration (Ms)
https://static.florr.io/be956309c38b570246a584a78a10cd5e7506f6d7/client.js	610	160

Show Details

Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of florr.io on mobile screens.

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 1.8 s
The time taken for the page contents to be visibly populated.

Other

Eliminate render-blocking resources — Potential savings of 500 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Florr.io should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

URL	Transfer Size (Bytes)	Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Ubuntu:700	1266	230

Show Details

Other

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

URL	Potential Savings (Ms)
https://fonts.gstatic.com/s/ubuntu/v19/4iCv6KVjbNBYlgoCxCvjsGyNPYZvgw.woff2	3.5799997858703

Show Details

Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Source
SHOW DETAILS

Show Details

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of florr.io. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.

The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.

Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.

`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.

ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.

ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.

ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.

`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Florr.io may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.

Failing Elements
html

Show Details

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Failing Elements
head > meta

Show Details

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.

Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.

Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.

The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.

User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.

Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.

Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.

Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.

Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.

HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that florr.io should incorporate. This includes practices such as protecting pages with HTTPS.

Passing (13)
Failing (3)

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).

Description	Directive	Severity
No CSP found in enforcement mode		High

Show Details

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.

Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.

Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.

Insecure URL	Request Resolution
http://florr.io/	Allowed

Show Details

Audits

Charset declaration is missing or occurs too late in the HTML
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Source	Description
SHOW DETAILS	WebSocket connection to 'wss://btk.s.m28n.net/' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
SHOW DETAILS	WebSocket connection to 'wss://bxo.s.m28n.net/' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED

Show Details

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for florr.io. This includes optimizations such as providing meta data.

Passing (14)
Manual Checks (1)

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of florr.io on mobile screens.

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.

Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.

Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.

Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of florr.io. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of florr.io on mobile screens.

Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.

Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.

Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

PWA

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: https://florr.io/

Updated: 30th March, 2022

1.89 seconds

First Contentful Paint (FCP)

74%

16%

10%

0.04 seconds

First Input Delay (FID)

87%

9%

4%

Simulate loading on mobile

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for florr.io. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 3.7 s
The time taken for the page to become fully interactive.

Total Blocking Time — 20 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 70 ms
Users could experience a delay when interacting with the page.

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://florr.io/	http/1.1	0	56.513000046834	714	0	301	text/plain
https://florr.io/	h2	56.765000103042	156.0490000993	2512	4429	200	text/html	Document
https://fonts.googleapis.com/css?family=Ubuntu:700	h2	171.34200013243	177.42200009525	1266	1728	200	text/css	Stylesheet
https://static.florr.io/be956309c38b570246a584a78a10cd5e7506f6d7/client.js	h2	180.5760001298	255.75400004163	38127	112596	200	text/plain	Script
https://fonts.gstatic.com/s/ubuntu/v19/4iCv6KVjbNBYlgoCxCvjsGyNPYZvgw.woff2	h2	181.61400011741	184.95499994606	15856	14928	200	font/woff2	Font
https://static.florr.io/be956309c38b570246a584a78a10cd5e7506f6d7/client.wasm	h2	269.53499997035	367.44599998929	514364	1795019	200	application/wasm	Fetch
https://api.n.m28.io/endpoint/florrio/findEach/	h2	682.62999993749	1047.1270000562	923	217	200	application/json	XHR
https://api.n.m28.io/endpoint/latency/findEach/	h2	1049.4580001105	1332.3260000907	1244	1326	200	application/json	XHR

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
201.571	7.855
221.75	5.119
305.615	7.161
410.847	6.312
417.333	234.452
651.816	7.292
659.651	10.6
674.011	8.09
690.699	8.111
708.116	8.332
724.114	9.585
740.746	10.453
757.436	8.504
774.11	9.802
790.878	10.068
807.454	12.717
824.051	8.63
840.763	8.424
857.501	10.883
876.347	9.748
890.721	8.716
907.376	11.004
924.087	8.959
940.696	8.484
957.528	10.858
974.066	8.564
990.814	8.654
1007.517	8.795
1024.115	11.975
1040.774	11.037
1057.406	11.66
1074.405	8.505
1092.681	9.59
1107.372	11.104
1124.214	10.783
1140.892	9.812
1157.448	9.442
1174.055	8.24
1190.663	8.275
1207.353	9.768
1224.097	7.959
1240.812	10.681
1257.4	8.908
1274.104	7.906
1290.759	8.653
1307.342	9.072
1324.039	8.993
1340.691	10.339
1357.402	8.941
1374.349	12.071
1390.665	8.484
1407.411	9.695
1424.122	10.949
1440.712	10.408
1457.382	9.825
1474.107	11.325
1490.851	8.14
1507.343	9.941
1523.99	7.446
1540.74	8.535
1557.67	9.192
1574.125	9.734
1590.698	8.411
1607.393	7.918
1624.059	8.611
1640.713	11.081
1657.309	10.155
1674.008	8.574
1690.754	10.023
1707.586	9.609
1724.051	10.25
1740.909	10.118
1757.376	9.33
1774.085	10.883
1790.669	8.313
1807.416	10.473
1824.015	8.991
1840.668	11.241
1857.409	8.926
1874.054	8.432
1890.765	10.273
1907.376	11.567
1924.059	8.698
1940.679	10.659
1957.446	10.686
1974.034	13.392
1990.728	8.4
2007.479	9.972
2024.092	11.246
2040.671	9.242
2057.335	8.096
2073.97	7.921
2090.706	7.926
2107.358	8.161
2124.931	9.29
2140.629	7.662
2157.36	8.713
2174.038	8.771
2190.72	8.896
2207.394	9.366
2224.064	8.943
2240.657	7.438
2257.523	17.285
2276.858	9.503
2290.688	8.662
2307.392	9.877
2324.405	9.273
2340.71	11.977
2357.296	9.005
2374.047	8.331
2390.656	8.438
2407.371	10.115
2424.056	7.706
2440.848	8.26
2457.374	7.978
2474.213	8.924
2490.705	9.376
2507.339	8.727
2524.154	11.381
2540.69	9.799
2557.294	8.651
2573.997	8.113
2590.683	9.503
2607.286	10.284
2623.983	8.969
2640.674	9.339
2657.35	8.717
2673.982	8.712
2690.659	8.886
2707.314	8.21
2724.019	8.654
2740.655	9.177
2757.32	8.267
2774.03	8.365
2790.683	8.261
2807.349	7.742
2824.079	7.733
2840.662	8.246
2857.326	9.173
2873.894	7.489
2890.598	9.421
2907.294	8.67
2924.048	8.274
2940.766	12.153
2957.301	7.868
2974.031	8.933
2990.773	9.03
3007.358	9.96
3023.976	9.039
3040.913	9.457
3057.552	10.093
3073.99	8.941
3090.655	9.079
3107.349	11.016
3123.96	12.593
3140.678	9.302
3157.328	9.485
3174.033	9.762
3190.731	9.965
3207.329	9.2
3224.636	9.875
3240.712	8.152
3257.277	9.457
3273.997	15.224
3290.772	9.525
3307.322	8.545
3324.128	10.709
3340.77	10.124
3358.519	11.38
3373.923	11.043
3390.892	11.218
3407.311	9.917
3423.999	8.286
3440.65	9.117
3457.337	8.789
3473.991	9.186
3490.684	9.72
3507.342	7.933
3523.92	8.759
3540.581	7.758
3557.626	9.333
3573.937	8.318
3590.781	9.618
3607.265	8.547
3623.984	10.938
3640.669	10.174
3657.289	8.204
3673.995	8.582
3690.618	7.631