lafenice.io

lafenice.io is SSL secured

Free website and domain report on lafenice.io

Last Updated: 1st June, 2021 Update Now
Overview

Snoop Summary for lafenice.io

This is a free and comprehensive report about lafenice.io. The domain lafenice.io is currently hosted on a server located in United States with the IP address 54.230.103.11, where the local currency is USD and English is the local language. Lafenice.io has the potential to be earning an estimated $1 USD per day from advertising revenue. If lafenice.io was to be sold it would possibly be worth $859 USD (based on the daily revenue potential of the website over a 24 month period). Lafenice.io receives an estimated 408 unique visitors every day - a decent amount of traffic! This report was last updated 1st June, 2021.

About lafenice.io

Site Preview: lafenice.io lafenice.io
Title:
Description:
Keywords and Tags:
Related Terms:
Fav Icon:
Age: Over 3 years old
Domain Created: 5th August, 2020
Domain Updated: 5th September, 2021
Domain Expires: 5th August, 2022
Review

Snoop Score

1/5

Valuation

$859 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,718,826
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: 408
Monthly Visitors: 12,418
Yearly Visitors: 148,920
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $35 USD
Yearly Revenue: $424 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: lafenice.io 11
Domain Name: lafenice 8
Extension (TLD): io 2
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 71
Performance 8
Accessibility 97
Best Practices 87
SEO 90
Progressive Web App 73
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
8

Performance

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

Metrics

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

Opportunities

Properly size images
Images can slow down the page's load time. Lafenice.io should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Lafenice.io should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Lafenice.io should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Lafenice.io should consider minifying JS files.
Remove unused CSS — Potential savings of 18 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Lafenice.io should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://lafenice.io/static/css/2.2b58c1d6.chunk.css
20041
18448
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Lafenice.io should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://lafenice.io/
190
https://lafenice.io/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Lafenice.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 — Potential savings of 27 KiB
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.
URL Potential Savings (Bytes)
https://lafenice.io/static/js/2.480aa5b6.chunk.js
22900
https://masacre.ladesk.com/scripts/track.js
5029
https://js.stripe.com/v3/
123
https://m.stripe.network/out-4.5.35.js
41
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Lafenice.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 — 1.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://lafenice.io/static/js/main.b69b39fa.chunk.js
555.738
480.167
43.052
https://lafenice.io/static/js/2.480aa5b6.chunk.js
509.919
313.844
104.769
https://script.hotjar.com/modules.db29179a0bade389a8b8.js
264.625
171.595
3.784
https://m.stripe.network/inner.html
109.248
101.917
0.906
Unattributable
76.925
4.418
0.204
https://lafenice.io/
73.487
4.876
2.308
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
68.398
32.437
27.527
Minimizes main-thread work — 1.9 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)
Script Evaluation
1294.024
Script Parsing & Compilation
209.121
Other
187.51
Garbage Collection
146.799
Parse HTML & CSS
35.106
Style & Layout
28.965
Rendering
10.88
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 44 requests • 9,681 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
44
9913523
Script
13
9803300
Stylesheet
4
31028
Other
20
26775
Document
5
19970
Image
1
19171
Font
1
13279
Media
0
0
Third-party
36
506631
Minimize third-party usage — Third-party code blocked the main thread for 60 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)
81215
49.767
64615
11.501
257630
0
36635
0
20814
0
14545
0
3761
0
687
0
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
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00018949710263778
0.00018402274189491
0.0001660836828452
4.8848142013295E-5
4.3851033232625E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
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 — 5 long tasks 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://lafenice.io/static/js/2.480aa5b6.chunk.js
8980
725
https://lafenice.io/static/js/2.480aa5b6.chunk.js
10069
299
https://m.stripe.network/out-4.5.35.js
1125
117
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
1415
104
https://script.hotjar.com/modules.db29179a0bade389a8b8.js
9979
90
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.

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.

Other

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://lafenice.io/
http/1.1
0
56.28600018099
449
0
301
text/html
https://lafenice.io/
h2
56.820000056177
777.53899991512
5145
4661
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-158531786-1
h2
794.06600026414
817.18300003558
36635
90747
200
application/javascript
Script
https://unpkg.com/leaflet@1.6.0/dist/leaflet.css
h2
794.29000010714
820.07900020108
3761
14268
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Oswald&display=swap
h2
794.51900022104
813.0330001004
1266
1764
200
text/css
Stylesheet
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
http/1.1
794.77800009772
934.52200014144
234346
1607807
200
application/javascript
Script
https://js.stripe.com/v3/
h2
794.98500004411
816.16100016981
57230
242885
200
application/javascript
Script
https://lafenice.io/static/css/2.2b58c1d6.chunk.css
h2
795.17400031909
898.34300009534
20041
19612
200
text/css
Stylesheet
https://lafenice.io/static/css/main.0e6a72d3.chunk.css
h2
795.37399997935
869.54900017008
5960
5532
200
text/css
Stylesheet
https://lafenice.io/static/js/2.480aa5b6.chunk.js
h2
795.58699997142
1058.999999892
6574338
6573893
200
application/javascript
Script
https://lafenice.io/static/js/main.b69b39fa.chunk.js
h2
795.82000011578
1014.7410002537
2549740
2549295
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1082.1060002781
1088.0260001868
20199
49153
200
text/javascript
Script
https://static.hotjar.com/c/hotjar-1493706.js?sv=6
h2
1082.3010001332
1097.2150000744
2442
4194
200
application/javascript
Script
https://masacre.ladesk.com/scripts/track.js
h2
1083.3850000054
1328.9370001294
14911
60067
200
application/javascript
Script
https://script.hotjar.com/modules.db29179a0bade389a8b8.js
h2
1110.483000055
1131.8780002184
59774
224798
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=1591898296&t=pageview&_s=1&dl=https%3A%2F%2Flafenice.io%2F&ul=en-us&de=UTF-8&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=668395228&gjid=1070899085&cid=533210752.1622555027&tid=UA-158531786-1&_gid=494208665.1622555027&_r=1&gtm=2ou5q1&z=1182787909
h2
1146.2690001354
1149.5010000654
615
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j90&tid=UA-158531786-1&cid=533210752.1622555027&jid=668395228&gjid=1070899085&_gid=494208665.1622555027&_u=YEBAAUAAAAAAAC~&z=1569431946
h2
1152.8270002455
1156.5249999985
687
1
200
text/plain
XHR
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
2081.0899999924
2151.665000245
610
0
200
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
2081.74100006
2483.0750003457
610
0
200
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
2082.4390002526
2175.6600001827
610
0
200
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
2083.5540001281
2232.8630001284
610
0
200
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
2084.1040001251
2156.3820000738
610
0
200
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
2152.3130000569
2245.968000032
690
116
401
application/json
Fetch
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
2483.7190001272
2527.2870003246
690
116
401
application/json
Fetch
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
2176.9139999524
2227.1740003489
690
116
401
application/json
Fetch
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
2233.6699999869
2314.3899999559
690
116
401
application/json
Fetch
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
2157.0880003273
2260.0960000418
690
116
401
application/json
Fetch
https://js.stripe.com/v3/m-outer-257db74dfc4594d2bb652dc7b646dbc5.html
h2
2098.2989999466
2113.7020001188
1037
215
200
text/html
Document
https://masacre.ladesk.com/scripts/track_visit.php?t=Y&C=Track&B=ic3qgoqurw13q5zbycgp48r0ubjcw&S=84vff4t6sai0rf5d7fz4te1yw9wad&pt=lafenice&url=__S__lafenice.io%2F&ref=&sr=800x600&ud=%7B%7D&vn=Y&ci=&jstk=Y
h2
2103.5270001739
2293.0590002798
795
602
200
application/x-javascript
Script
https://hocx8gfype.execute-api.us-east-1.amazonaws.com/prd/app-version
h2
2123.4599999152
2310.1290003397
327
33
200
application/json
XHR
https://hocx8gfype.execute-api.us-east-1.amazonaws.com/prd/referral
h2
2124.4780002162
2274.2570000701
16085
15788
200
application/json
XHR
https://js.stripe.com/v3/fingerprinted/js/m-outer-b07c750376b94b0da646edc72e01a46a.js
h2
2137.3250000179
2152.8170001693
1600
1443
200
application/javascript
Script
https://vars.hotjar.com/box-21ccaa45726c0f3c8c458f7a87eb2298.html
h2
2147.530999966
2163.2699999027
1598
2431
200
text/html
Document
data
2146.1900002323
2146.2730001658
0
284
200
image/jpeg
Image
https://m.stripe.network/inner.html
h2
2159.6150002442
2175.8600003086
1441
932
200
text/html
Document
https://in.hotjar.com/api/v2/client/sites/1493706/visit-data?sv=6
h2
2194.3129999563
2299.138000235
408
171
200
application/json
XHR
https://m.stripe.network/out-4.5.35.js
h2
2222.3730003461
2241.5479999036
19242
86953
200
application/x-javascript
Script
https://lafenice.io/static/js/3.acf69e38.chunk.js
h2
2434.931000229
2610.9960000031
232048
231610
200
application/javascript
Script
https://lafenice.io/static/media/flags.5c58d0e1.png
h2
2677.3860002868
2775.1670000143
19171
18747
200
image/png
Image
https://fonts.gstatic.com/s/oswald/v36/TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYySUhiCXAA.woff
h2
2679.6070002019
2683.2330003381
13279
12672
200
font/woff
Font
https://ws16.hotjar.com/api/v2/sites/1493706/recordings/content
http/1.1
2787.2629999183
3728.1160000712
393
66
200
application/json
XHR
https://hocx8gfype.execute-api.us-east-1.amazonaws.com/prd/app-config?type=allowRegister
h2
2793.1230003014
2951.3870002702
372
78
200
application/json
XHR
https://m.stripe.com/6
h2
2808.8380000554
2919.740000274
665
156
200
text/plain
XHR
https://1-vbus-us-tx.ladesk.com/5_23_20_3/scripts/lib/bus.html?v=5.23.20.3
h2
2870.5710000359
2991.22299999
10749
34476
200
text/html
Document
https://1-vbus-us-tx.ladesk.com/5_23_20_3/u239025_4ff7/ic3qgoqurw13q5zbycgp48r0ubjcw/event/lp/v2?channels=b2dcd0df16_vb_84vff4t6sai0rf5d7fz4te1yw9wad&tag=0&time=Tue%2C%2001%20Jun%202021%2009%3A33%3A48%20GMT&eventid=&_=1622555028909
h2
3023.0050003156
3140.2170001529
274
0
304
XHR
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)
813.517
8.867
859.488
13.223
873.121
14.038
1012.465
103.897
1119.568
6.533
1126.278
11.07
1144.698
34.612
1191.148
24.612
1365.9
13.924
1393.303
725.288
2121.646
11.617
2141.841
14.77
2158.442
7.904
2198.947
7.933
2214.201
6.696
2220.957
28.664
2261.164
10.852
2279.758
6.277
2288.637
117.21
2408.417
298.923
2707.366
19.628
2730.073
90.281
2830.752
9.538
2855.862
5.906
2862.387
35.174
2898.391
8.579
2908.834
27.16
2939.707
9.842
2949.714
32.657
2992.746
9.837
3027.613
7.307
3040.561
5.913
3049.444
5.581
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 560 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Lafenice.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://unpkg.com/leaflet@1.6.0/dist/leaflet.css
3761
230
https://fonts.googleapis.com/css?family=Oswald&display=swap
1266
230
https://lafenice.io/static/css/2.2b58c1d6.chunk.css
20041
80
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
234346
750
https://js.stripe.com/v3/
57230
430

Diagnostics

Avoid an excessive DOM size — 1,329 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
1329
Maximum DOM Depth
div
12
Maximum Child Elements
258

Metrics

First Contentful Paint — 9.0 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 9.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 9.8 s
The timing of the largest text or image that is painted.
Time to Interactive — 10.3 s
The time taken for the page to become fully interactive.
Total Blocking Time — 860 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).

Other

First CPU Idle — 9.0 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 730 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 9.0 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 220 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive lafenice.io as laggy when the latency is higher than 0.05 seconds.

Opportunities

Remove unused JavaScript — Potential savings of 6,209 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://lafenice.io/static/js/2.480aa5b6.chunk.js
6574338
5333083
https://lafenice.io/static/js/main.b69b39fa.chunk.js
2549740
732109
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
234346
218857
https://js.stripe.com/v3/
57230
43948
https://script.hotjar.com/modules.db29179a0bade389a8b8.js
59774
30061
Enable text compression — Potential savings of 7,108 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://lafenice.io/static/js/2.480aa5b6.chunk.js
6573893
5172830
https://lafenice.io/static/js/main.b69b39fa.chunk.js
2549295
1890804
https://lafenice.io/static/js/3.acf69e38.chunk.js
231610
180156
https://lafenice.io/static/css/2.2b58c1d6.chunk.css
19612
16524
https://hocx8gfype.execute-api.us-east-1.amazonaws.com/prd/referral
15788
12165
https://lafenice.io/static/css/main.0e6a72d3.chunk.css
5532
3972
https://lafenice.io/
4661
2408
Reduce initial server response time — Root document took 720 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://lafenice.io/
721.717

Diagnostics

Avoid enormous network payloads — Total size was 9,681 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://lafenice.io/static/js/2.480aa5b6.chunk.js
6574338
https://lafenice.io/static/js/main.b69b39fa.chunk.js
2549740
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
234346
https://lafenice.io/static/js/3.acf69e38.chunk.js
232048
https://script.hotjar.com/modules.db29179a0bade389a8b8.js
59774
https://js.stripe.com/v3/
57230
https://www.googletagmanager.com/gtag/js?id=UA-158531786-1
36635
https://www.google-analytics.com/analytics.js
20199
https://lafenice.io/static/css/2.2b58c1d6.chunk.css
20041
https://m.stripe.network/out-4.5.35.js
19242
Serve static assets with an efficient cache policy — 13 resources found
Lafenice.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://lafenice.io/static/js/2.480aa5b6.chunk.js
0
6574338
https://lafenice.io/static/js/main.b69b39fa.chunk.js
0
2549740
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
0
234346
https://lafenice.io/static/js/3.acf69e38.chunk.js
0
232048
https://lafenice.io/static/css/2.2b58c1d6.chunk.css
0
20041
https://lafenice.io/static/media/flags.5c58d0e1.png
0
19171
https://lafenice.io/static/css/main.0e6a72d3.chunk.css
0
5960
https://static.hotjar.com/c/hotjar-1493706.js?sv=6
60000
2442
https://js.stripe.com/v3/
300000
57230
https://m.stripe.network/out-4.5.35.js
300000
19242
https://masacre.ladesk.com/scripts/track.js
300000
14911
https://js.stripe.com/v3/fingerprinted/js/m-outer-b07c750376b94b0da646edc72e01a46a.js
300000
1600
https://www.google-analytics.com/analytics.js
7200000
20199
97

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of lafenice.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 `[alt]` 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.

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

Audio and video

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

Contrast

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

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.
87

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.

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.
Properly defines charset
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

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.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
Leaflet
1.6.0
Hammer.js
2.0.7
core-js
core-js-pure@2.6.11
Create React App
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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://lafenice.io/
Allowed

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
Failed to load resource: the server responded with a status of 401 (Unauthorized)
Failed to load resource: the server responded with a status of 401 (Unauthorized)
Failed to load resource: the server responded with a status of 401 (Unauthorized)
Failed to load resource: the server responded with a status of 401 (Unauthorized)
Failed to load resource: the server responded with a status of 401 (Unauthorized)
WebSocket connection to 'wss://ws16.hotjar.com/api/v2/client/ws' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://lafenice.io/static/js/main.b69b39fa.chunk.js
https://lafenice.io/static/js/2.480aa5b6.chunk.js
90

SEO

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

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 lafenice.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.
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.

Content Best Practices

Document does not have 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.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
73

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of lafenice.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

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 lafenice.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) 71
Performance 5
Accessibility 97
Best Practices 87
SEO 92
Progressive Web App 75
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://lafenice.io/
Updated: 1st June, 2021

4.83 seconds
First Contentful Paint (FCP)
4%
48%
48%

0.01 seconds
First Input Delay (FID)
98%
1%
1%

Simulate loading on mobile
5

Performance

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

Metrics

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

Opportunities

Properly size images
Images can slow down the page's load time. Lafenice.io should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Lafenice.io should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Lafenice.io should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Lafenice.io should consider minifying JS files.
Remove unused CSS — Potential savings of 18 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Lafenice.io should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://lafenice.io/static/css/2.2b58c1d6.chunk.css
20041
18185
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Lafenice.io should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://lafenice.io/
630
https://lafenice.io/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Lafenice.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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Lafenice.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.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 45 requests • 9,712 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
45
9945085
Script
13
9803209
Image
1
53416
Stylesheet
4
31016
Other
21
27109
Document
5
19969
Font
1
10366
Media
0
0
Third-party
37
503942
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
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0020362199974345
0.0010779988221712
0.00049622168004707
0.000445458772548
0.00026864415092203
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
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 — 11 long tasks 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://lafenice.io/static/js/2.480aa5b6.chunk.js
51960
2636
https://lafenice.io/static/js/2.480aa5b6.chunk.js
55721
909
https://m.stripe.network/out-4.5.35.js
4641
446
https://m.stripe.network/out-4.5.35.js
5087
363
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
6411
312
https://lafenice.io/static/js/2.480aa5b6.chunk.js
56630
121
https://lafenice.io/static/js/3.acf69e38.chunk.js
57980
114
https://js.stripe.com/v3/
54641
96
https://script.hotjar.com/modules.db29179a0bade389a8b8.js
9033
87
https://www.google-analytics.com/analytics.js
3924
76
https://www.googletagmanager.com/gtag/js?id=UA-158531786-1
39360
59
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.

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.

Other

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://lafenice.io/
http/1.1
0
59.551000129431
449
0
301
text/html
https://lafenice.io/
h2
59.990000445396
738.78700006753
5145
4661
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-158531786-1
h2
752.28200014681
771.16000000387
36631
90747
200
application/javascript
Script
https://unpkg.com/leaflet@1.6.0/dist/leaflet.css
h2
752.59200017899
805.32300006598
3765
14268
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Oswald&display=swap
h2
752.76300031692
767.61000044644
1250
1763
200
text/css
Stylesheet
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
http/1.1
753.04700015113
833.86200014502
234251
1607807
200
application/javascript
Script
https://js.stripe.com/v3/
h2
753.39299999177
773.54399999604
57229
242885
200
application/javascript
Script
https://lafenice.io/static/css/2.2b58c1d6.chunk.css
h2
753.73500026762
836.82000031695
20041
19612
200
text/css
Stylesheet
https://lafenice.io/static/css/main.0e6a72d3.chunk.css
h2
753.95900011063
792.93300025165
5960
5532
200
text/css
Stylesheet
https://lafenice.io/static/js/2.480aa5b6.chunk.js
h2
754.18200017884
1059.4530003145
6574338
6573893
200
application/javascript
Script
https://lafenice.io/static/js/main.b69b39fa.chunk.js
h2
754.55400021747
1105.0960002467
2549740
2549295
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
956.06200024486
962.86100009456
20199
49153
200
text/javascript
Script
https://static.hotjar.com/c/hotjar-1493706.js?sv=6
h2
956.23100036755
973.40500028804
2443
4194
200
application/javascript
Script
https://masacre.ladesk.com/scripts/track.js
h2
956.86900010332
1108.619000297
14911
60067
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=1303845237&t=pageview&_s=1&dl=https%3A%2F%2Flafenice.io%2F&ul=en-us&de=UTF-8&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=126799200&gjid=450476194&cid=227468987.1622555052&tid=UA-158531786-1&_gid=2058831609.1622555052&_r=1&gtm=2ou5q1&z=1524982086
h2
985.29600026086
1016.9700002298
615
2
200
text/plain
XHR
https://script.hotjar.com/modules.db29179a0bade389a8b8.js
h2
988.73200034723
1006.8800002337
59774
224798
200
application/javascript
Script
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j90&tid=UA-158531786-1&cid=227468987.1622555052&jid=126799200&gjid=450476194&_gid=2058831609.1622555052&_u=YEBAAUAAAAAAAC~&z=883060308
h2
1038.9500004239
1068.8550001942
687
1
200
text/plain
XHR
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
1932.6970004477
1962.3520001769
610
0
200
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
1933.0410002731
1965.4290000908
610
0
200
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
1933.3140002564
1996.9220003113
610
0
200
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
1933.8020002469
1996.0000002757
610
0
200
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
1934.4370001927
1996.5130002238
610
0
200
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
1962.9360004328
2042.4860003404
690
116
401
application/json
Fetch
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
1965.8360001631
2004.3740002438
690
116
401
application/json
Fetch
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
1997.9010000825
2052.6200002059
690
116
401
application/json
Fetch
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
1996.710000094
2055.757000111
690
116
401
application/json
Fetch
https://lv64xbqsp5bclkvvw7mvt5k7qi.appsync-api.us-east-1.amazonaws.com/graphql
h2
1997.1080003306
2036.929000169
690
116
401
application/json
Fetch
https://js.stripe.com/v3/m-outer-257db74dfc4594d2bb652dc7b646dbc5.html
h2
1951.446000021
1966.7330002412
1036
215
200
text/html
Document
https://masacre.ladesk.com/scripts/track_visit.php?t=Y&C=Track&B=hl427s9jpaih93qwaqttu2xjdo9bh&S=fba4va0o3mz1rocwxx0zde0e108js&pt=lafenice&url=__S__lafenice.io%2F&ref=&sr=360x640&ud=%7B%7D&vn=Y&ci=&jstk=Y
h2
1961.4180000499
1993.891000282
796
602
200
application/x-javascript
Script
https://hocx8gfype.execute-api.us-east-1.amazonaws.com/prd/app-version
h2
1982.0170002058
2123.3220002614
327
33
200
application/json
XHR
https://hocx8gfype.execute-api.us-east-1.amazonaws.com/prd/referral
h2
1982.8610001132
2150.2740001306
16085
15788
200
application/json
XHR
https://js.stripe.com/v3/fingerprinted/js/m-outer-b07c750376b94b0da646edc72e01a46a.js
h2
1992.7480001934
2007.706000004
1601
1443
200
application/javascript
Script
https://1-vbus-us-tx.ladesk.com/5_23_20_3/scripts/lib/bus.html?v=5.23.20.3
h2
2000.9640003555
2036.4720001817
10749
34476
200
text/html
Document
https://vars.hotjar.com/box-21ccaa45726c0f3c8c458f7a87eb2298.html
h2
2007.337000221
2030.0130001269
1598
2431
200
text/html
Document
https://m.stripe.network/inner.html
h2
2017.2940003686
2033.0040003173
1441
932
200
text/html
Document
data
2020.3770003282
2020.4620002769
0
284
200
image/jpeg
Image
https://m.stripe.network/out-4.5.35.js
h2
2072.458000388
2087.8210002556
19242
86953
200
application/x-javascript
Script
https://in.hotjar.com/api/v2/client/sites/1493706/visit-data?sv=6
h2
2094.9950003996
2202.8370001353
409
175
200
application/json
XHR
https://1-vbus-us-tx.ladesk.com/5_23_20_3/u239025_4ff7/hl427s9jpaih93qwaqttu2xjdo9bh/event/lp/v2?channels=b2dcd0df16_vb_fba4va0o3mz1rocwxx0zde0e108js&tag=0&time=Tue%2C%2001%20Jun%202021%2009%3A34%3A13%20GMT&eventid=&_=1622555053411
h2
2118.4190004133
2149.3470002897
274
0
304
XHR
https://hocx8gfype.execute-api.us-east-1.amazonaws.com/prd/app-config?type=allowRegister
h2
2234.6320003271
2331.6890001297
372
78
200
application/json
XHR
https://lafenice.io/static/js/3.acf69e38.chunk.js
h2
2281.3820000738
2386.9870002382
232054
231610
200
application/javascript
Script
https://lafenice.io/static/media/flags@2x.27670c53.png
h2
2464.3560000695
2576.9310002215
53416
52992
200
image/png
Image
https://fonts.gstatic.com/s/oswald/v36/TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiZSSShiA.woff2
h2
2467.7870003507
2470.4460003413
10366
9772
200
font/woff2
Font
https://hocx8gfype.execute-api.us-east-1.amazonaws.com/prd/app-version
h2
2485.9000002034
2541.5600002743
327
33
200
application/json
XHR
https://m.stripe.com/6
h2
2584.7580004483
2674.3110003881
666
156
200
text/plain
XHR
https://ws3.hotjar.com/api/v2/sites/1493706/recordings/content
http/1.1
2630.4300003685
3531.3610001467
398
66
200
application/json
XHR
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)
769.397
7.132
778.285
5.159
806.529
9.686
816.886
8.147
906.947
78.091
994.297
18.962
1042.853
21.701
1094.117
9.583
1135.25
5.151
1144.045
8.026
1306.887
659.07
1971.673
14.686
1993.356
5.289
1998.698
11.329
2010.043
6.976
2023.283
8.08
2054.976
6.357
2061.345
5.703
2067.174
5.626
2073.53
6.968
2118.259
24.072
2148.244
111.416
2263.016
227.152
2490.203
17.147
2514.455
7.079
2521.545
90.661
2616.427
30.193
2661.16
5.203
2671.495
28.586
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Avoid serving legacy JavaScript to modern browsers — Potential savings of 27 KiB
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.
URL Potential Savings (Bytes)
https://lafenice.io/static/js/2.480aa5b6.chunk.js
22900
https://masacre.ladesk.com/scripts/track.js
5029
https://js.stripe.com/v3/
123
https://m.stripe.network/out-4.5.35.js
41

Diagnostics

Avoid an excessive DOM size — 1,329 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
1329
Maximum DOM Depth
div
12
Maximum Child Elements
258

Metrics

First Contentful Paint — 52.1 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 52.1 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 55.2 s
The timing of the largest text or image that is painted.
Time to Interactive — 57.7 s
The time taken for the page to become fully interactive.
Total Blocking Time — 3,100 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).

Other

First CPU Idle — 52.2 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 2,640 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 52.2 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 1,720 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive lafenice.io as laggy when the latency is higher than 0.05 seconds.
First Contentful Paint (3G) — 116696 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 2,680 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Lafenice.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://unpkg.com/leaflet@1.6.0/dist/leaflet.css
3765
780
https://fonts.googleapis.com/css?family=Oswald&display=swap
1250
780
https://lafenice.io/static/css/2.2b58c1d6.chunk.css
20041
600
https://lafenice.io/static/css/main.0e6a72d3.chunk.css
5960
150
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
234251
3780
https://js.stripe.com/v3/
57229
1980
Remove unused JavaScript — Potential savings of 6,209 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://lafenice.io/static/js/2.480aa5b6.chunk.js
6574338
5333083
https://lafenice.io/static/js/main.b69b39fa.chunk.js
2549740
732109
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
234251
218768
https://js.stripe.com/v3/
57229
43947
https://script.hotjar.com/modules.db29179a0bade389a8b8.js
59774
30061
Enable text compression — Potential savings of 7,108 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://lafenice.io/static/js/2.480aa5b6.chunk.js
6573893
5172830
https://lafenice.io/static/js/main.b69b39fa.chunk.js
2549295
1890804
https://lafenice.io/static/js/3.acf69e38.chunk.js
231610
180156
https://lafenice.io/static/css/2.2b58c1d6.chunk.css
19612
16524
https://hocx8gfype.execute-api.us-east-1.amazonaws.com/prd/referral
15788
12165
https://lafenice.io/static/css/main.0e6a72d3.chunk.css
5532
3972
https://lafenice.io/
4661
2408
Reduce initial server response time — Root document took 680 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://lafenice.io/
679.796

Diagnostics

Avoid enormous network payloads — Total size was 9,712 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://lafenice.io/static/js/2.480aa5b6.chunk.js
6574338
https://lafenice.io/static/js/main.b69b39fa.chunk.js
2549740
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
234251
https://lafenice.io/static/js/3.acf69e38.chunk.js
232054
https://script.hotjar.com/modules.db29179a0bade389a8b8.js
59774
https://js.stripe.com/v3/
57229
https://lafenice.io/static/media/flags@2x.27670c53.png
53416
https://www.googletagmanager.com/gtag/js?id=UA-158531786-1
36631
https://www.google-analytics.com/analytics.js
20199
https://lafenice.io/static/css/2.2b58c1d6.chunk.css
20041
Serve static assets with an efficient cache policy — 13 resources found
Lafenice.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://lafenice.io/static/js/2.480aa5b6.chunk.js
0
6574338
https://lafenice.io/static/js/main.b69b39fa.chunk.js
0
2549740
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
0
234251
https://lafenice.io/static/js/3.acf69e38.chunk.js
0
232054
https://lafenice.io/static/media/flags@2x.27670c53.png
0
53416
https://lafenice.io/static/css/2.2b58c1d6.chunk.css
0
20041
https://lafenice.io/static/css/main.0e6a72d3.chunk.css
0
5960
https://static.hotjar.com/c/hotjar-1493706.js?sv=6
60000
2443
https://js.stripe.com/v3/
300000
57229
https://m.stripe.network/out-4.5.35.js
300000
19242
https://masacre.ladesk.com/scripts/track.js
300000
14911
https://js.stripe.com/v3/fingerprinted/js/m-outer-b07c750376b94b0da646edc72e01a46a.js
300000
1601
https://www.google-analytics.com/analytics.js
7200000
20199
Reduce JavaScript execution time — 4.9 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://lafenice.io/static/js/main.b69b39fa.chunk.js
2044.196
1731.228
153.744
https://lafenice.io/static/js/2.480aa5b6.chunk.js
1762.348
1055.336
385.66
https://m.stripe.network/inner.html
781.26
512.92
3.54
Unattributable
357.292
100.976
0.9
https://script.hotjar.com/modules.db29179a0bade389a8b8.js
271
225.488
14.836
https://lafenice.io/
240.828
19.592
7.82
https://sdk.amazonaws.com/js/aws-sdk-2.167.0.min.js
211.996
84.68
92.964
https://lafenice.io/static/js/3.acf69e38.chunk.js
113.468
92.852
13.88
https://js.stripe.com/v3/
111.456
90.292
15.504
https://m.stripe.network/out-4.5.35.js
90.42
72.048
6.932
https://www.google-analytics.com/analytics.js
88.136
72.584
4.704
https://www.googletagmanager.com/gtag/js?id=UA-158531786-1
83.396
63.052
10.132
https://js.stripe.com/v3/m-outer-257db74dfc4594d2bb652dc7b646dbc5.html
54.932
7.28
4.22
https://masacre.ladesk.com/scripts/track.js
50.272
41.184
6.452
Minimize main-thread work — 6.4 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)
Script Evaluation
4263.06
Script Parsing & Compilation
745.28
Other
671.26
Garbage Collection
494.124
Style & Layout
134.588
Parse HTML & CSS
103.284
Rendering
28.364
Reduce the impact of third-party code — Third-party code blocked the main thread for 700 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)
81215
552.432
257862
76.796
64622
54.032
20814
17.236
36631
0
11616
0
3765
0
687
0
97

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of lafenice.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 `[alt]` 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.

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

Audio and video

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

Contrast

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

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.
87

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.

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.
Properly defines charset
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

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.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
Leaflet
1.6.0
Hammer.js
2.0.7
core-js
core-js-pure@2.6.11
Create React App
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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://lafenice.io/
Allowed

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
Failed to load resource: the server responded with a status of 401 (Unauthorized)
Failed to load resource: the server responded with a status of 401 (Unauthorized)
Failed to load resource: the server responded with a status of 401 (Unauthorized)
Failed to load resource: the server responded with a status of 401 (Unauthorized)
Failed to load resource: the server responded with a status of 401 (Unauthorized)
WebSocket connection to 'wss://ws3.hotjar.com/api/v2/client/ws' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://lafenice.io/static/js/main.b69b39fa.chunk.js
https://lafenice.io/static/js/2.480aa5b6.chunk.js
92

SEO

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

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 lafenice.io on mobile screens.
Document uses legible font sizes — 99.22% legible text
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.
Source Selector % of Page Text Font Size
.intl-tel-input .flag-container .arrow
0.78%
6px
99.22%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
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.
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.

Content Best Practices

Document does not have 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.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
75

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of lafenice.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

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 lafenice.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.
Hosting

Server Location

Server IP Address: 54.230.103.11
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Amazon.com, Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.207.7.116
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: lafenice.io
Issued By: Amazon
Valid From: 12th April, 2021
Valid To: 11th May, 2022
Subject: CN = lafenice.io
Hash: c19e4fbb
Issuer: CN = Amazon
OU = Server CA 1B
O = Amazon
S = US
Version: 2
Serial Number: 14590180541279033425184592006439527387
Serial Number (Hex): 0AF9F770775274AC2B98A88802D863DB
Valid From: 12th April, 2024
Valid To: 11th May, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:59:A4:66:06:52:A0:7B:95:92:3C:A3:94:07:27:96:74:5B:F9:3D:D0
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.sca1b.amazontrust.com/sca1b.crl

Certificate Policies: Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://ocsp.sca1b.amazontrust.com
CA Issuers - URI:http://crt.sca1b.amazontrust.com/sca1b.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Apr 12 02:46:50.490 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:A9:CB:8B:78:48:E4:6E:72:30:2C:EB:
EC:F9:EA:0A:A6:07:54:5A:38:1C:D6:35:E2:C0:85:34:
60:4B:30:FD:85:02:21:00:B4:D9:2F:59:4F:C7:C9:F6:
0F:4B:E1:D2:57:C6:B0:EE:4D:87:CF:72:F6:57:31:9D:
ED:1E:6E:68:E0:3D:30:A4
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 22:45:45:07:59:55:24:56:96:3F:A1:2F:F1:F7:6D:86:
E0:23:26:63:AD:C0:4B:7F:5D:C6:83:5C:6E:E2:0F:02
Timestamp : Apr 12 02:46:50.451 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:F4:09:B3:02:80:55:6A:98:AA:B1:4C:
EB:E9:04:A0:43:0D:34:47:16:5F:93:93:39:E4:CA:8A:
59:39:84:B5:03:02:20:60:5E:12:7D:EE:87:E1:E2:B0:
03:5C:0F:7C:EA:82:74:FC:7F:C4:25:E8:5B:2D:49:17:
E5:AC:A9:54:BD:80:F2
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 51:A3:B0:F5:FD:01:79:9C:56:6D:B8:37:78:8F:0C:A4:
7A:CC:1B:27:CB:F7:9E:88:42:9A:0D:FE:D4:8B:05:E5
Timestamp : Apr 12 02:46:50.485 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:07:C4:98:C8:6D:65:6E:04:90:52:2F:EF:
0B:95:D7:E1:00:B7:02:50:E6:8E:5A:CD:C2:B1:FE:6B:
A3:E8:FC:23:02:20:5C:69:F4:7B:1E:C3:F5:2F:03:55:
A7:BD:FF:25:24:34:24:DD:0F:9B:F9:67:D8:3D:22:EC:
FD:98:CA:23:FA:6A
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.lafenice.io
DNS:lafenice.io
Technical

DNS Lookup

A Records

Host IP Address Class TTL
lafenice.io. 52.85.132.75 IN 59
lafenice.io. 52.85.132.40 IN 59
lafenice.io. 52.85.132.16 IN 59
lafenice.io. 52.85.132.129 IN 59

NS Records

Host Nameserver Class TTL
lafenice.io. ns-1498.awsdns-59.org. IN 21599
lafenice.io. ns-1587.awsdns-06.co.uk. IN 21599
lafenice.io. ns-551.awsdns-04.net. IN 21599
lafenice.io. ns-93.awsdns-11.com. IN 21599

SOA Records

Domain Name Primary NS Responsible Email TTL
lafenice.io. ns-93.awsdns-11.com. awsdns-hostmaster.amazon.com. 899

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Content-Type: text/html
Date: 1st June, 2021
Cache-Control: max-age=0,no-cache,no-store,must-revalidate
Server: AmazonS3
Content-Length: 4661
Connection: keep-alive
Last-Modified: 28th May, 2021
ETag: "5477d476fe681410ab11c0c8144fb07a"
Accept-Ranges: bytes
X-Cache: Error from cloudfront
Via: 1.1 1322f71561d45d48a5334ac75abd0c2f.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: EWR53-C3
X-Amz-Cf-Id: lAGLgUyaQNRw_frgCALhtElW2tIV5CL8YIottnqIVjbBypROUsYZlw==

Whois Lookup

Created: 5th August, 2020
Changed: 5th September, 2021
Expires: 5th August, 2022
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns-1498.awsdns-59.org
ns-1587.awsdns-06.co.uk
ns-551.awsdns-04.net
ns-93.awsdns-11.com
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
14455 N. Hayden Road
Owner Post Code: 85260
Owner City: Scottsdale
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: lafenice.io@domainsbyproxy.com
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
14455 N. Hayden Road
Admin Post Code: 85260
Admin City: Scottsdale
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: lafenice.io@domainsbyproxy.com
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
14455 N. Hayden Road
Tech Post Code: 85260
Tech City: Scottsdale
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: lafenice.io@domainsbyproxy.com
Full Whois: Domain Name: lafenice.io
Registry Domain ID: D503300001185341312-LRMS
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2021-05-09T12:58:46Z
Creation Date: 2020-05-08T16:02:08Z
Registrar Registration Expiration Date: 2022-05-08T16:02:08Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited
Registry Registrant ID: CR422947373
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 14455 N. Hayden Road
Registrant City: Scottsdale
Registrant State/Province: Arizona
Registrant Postal Code: 85260
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: lafenice.io@domainsbyproxy.com
Registry Tech ID: CR422947374
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 14455 N. Hayden Road
Tech City: Scottsdale
Tech State/Province: Arizona
Tech Postal Code: 85260
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: lafenice.io@domainsbyproxy.com
Registry Admin ID: CR422947375
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 14455 N. Hayden Road
Admin City: Scottsdale
Admin State/Province: Arizona
Admin Postal Code: 85260
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: lafenice.io@domainsbyproxy.com
Name Server: NS-93.AWSDNS-11.COM
Name Server: NS-1587.AWSDNS-06.CO.UK
Name Server: NS-1498.AWSDNS-59.ORG
Name Server: NS-551.AWSDNS-04.NET
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-06-01T13:43:42Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
ns-1498.awsdns-59.org 205.251.197.218
ns-1587.awsdns-06.co.uk 205.251.198.51
ns-551.awsdns-04.net 205.251.194.39
ns-93.awsdns-11.com 205.251.192.93
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$12,988 USD 3/5