Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

playalinda.com

playalinda.com is SSL secured

Free website and domain report on playalinda.com

Last Updated: 9th August, 2021 Update Now
Overview

Snoop Summary for playalinda.com

This is a free and comprehensive report about playalinda.com. The domain playalinda.com is currently hosted on a server located in United States with the IP address 75.2.60.5, where USD is the local currency and the local language is English. Playalinda.com has the potential to be earning an estimated $3 USD per day from advertising revenue. If playalinda.com was to be sold it would possibly be worth $2,240 USD (based on the daily revenue potential of the website over a 24 month period). Playalinda.com receives an estimated 1,072 unique visitors every day - a large amount of traffic! This report was last updated 9th August, 2021.

About playalinda.com

Site Preview: playalinda.com playalinda.com
Title: Playa Linda Beach Resort
Description: Playa Linda Beach Resort
Keywords and Tags: travel
Related Terms: linda harden, linda ikeji, linda ikeji blog, linda kozlowski, linda lysell, linda thorson, linda vacatures, linda woodrow, listen linda, playa alojera
Fav Icon:
Age: Over 26 years old
Domain Created: 19th September, 1997
Domain Updated: 24th June, 2021
Domain Expires: 18th September, 2022
Review

Snoop Score

2/5

Valuation

$2,240 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 771,555
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 1,072
Monthly Visitors: 32,628
Yearly Visitors: 391,280
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $3 USD
Monthly Revenue: $93 USD
Yearly Revenue: $1,115 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: playalinda.com 14
Domain Name: playalinda 10
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 92
Performance 84
Accessibility 100
Best Practices 93
SEO 100
Progressive Web App 82
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.playalinda.com/
Updated: 9th August, 2021

1.08 seconds
First Contentful Paint (FCP)
92%
4%
4%

0.00 seconds
First Input Delay (FID)
99%
0%
1%

Simulate loading on desktop
84

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 90 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://playalinda.com/
http/1.1
0
166.62199981511
337
0
301
text/plain
https://playalinda.com/
http/1.1
167.45399963111
576.27199962735
390
0
301
text/plain
https://www.playalinda.com/
h2
576.9269997254
1036.0019998625
45819
146332
200
text/html
Document
https://www.playalinda.com/webpack-runtime-ec4ba749219663bc2f8f.js
h2
1050.9769995697
1194.6159997024
3026
5380
200
application/javascript
Script
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js
h2
1051.4429998584
1459.6329997294
45109
148224
200
application/javascript
Script
https://www.playalinda.com/app-8d572199f93af02e0d57.js
h2
1051.8509997055
1197.9339998215
71520
312666
200
application/javascript
Script
https://www.playalinda.com/1bfc9850-4f063d657ae861026224.js
h2
1052.0929996856
1333.3139996976
1219
856
200
application/javascript
Script
https://www.playalinda.com/d7eeaac4-9008aa8b67b154adcf61.js
h2
1052.5209996849
1332.8389995731
1024
661
200
application/javascript
Script
https://www.playalinda.com/0c428ae2-86697eaead34d26e7ff5.js
h2
1052.8769996017
1333.8809995912
1220
2747
200
application/javascript
Script
https://www.playalinda.com/17007de1-558c070d1c7666980cdb.js
h2
1053.172999993
1195.1419999823
1092
729
200
application/javascript
Script
https://www.playalinda.com/commons-119a607f4be1340eaf26.js
h2
1053.5149998032
1534.3700000085
88134
316685
200
application/javascript
Script
https://www.playalinda.com/f143af7d537af45a50ebbb3b8b4b7a28bb3023a8-e852cd01c0d35bf5790b.js
h2
1053.7979998626
1336.4039999433
5873
16012
200
application/javascript
Script
https://www.playalinda.com/component---src-pages-index-tsx-aba1639435ce1c619a8f.js
h2
1054.0399998426
1334.4049998559
7057
23125
200
application/javascript
Script
https://www.playalinda.com/page-data/index/page-data.json
h2
1054.4489999302
1195.479999762
534
192
200
application/json
Other
https://www.playalinda.com/page-data/sq/d/1001606710.json
h2
1054.7529999167
1195.8739999682
3216
14238
200
application/json
Other
https://www.playalinda.com/page-data/sq/d/2686767999.json
h2
1054.9879996106
1336.9329995476
2069
9736
200
application/json
Other
https://www.playalinda.com/page-data/sq/d/379716309.json
h2
1055.1979998127
1763.8379996642
31480
51084
200
application/json
Other
https://www.playalinda.com/page-data/sq/d/3841368162.json
h2
1055.5739998817
1334.7579999827
876
1465
200
application/json
Other
https://www.playalinda.com/page-data/sq/d/4229546192.json
h2
1055.9859997593
1335.5619995855
432
91
200
application/json
Other
https://www.playalinda.com/page-data/sq/d/63159454.json
h2
1056.3599998131
1335.8249999583
461
119
200
application/json
Other
https://www.playalinda.com/page-data/app-data.json
h2
1056.6019997932
1335.2159997448
391
50
200
application/json
Other
https://www.playalinda.com/static/Moderat-Medium-70a70082030b96d40bfa454c1a49243f.woff2
h2
1088.9829997905
1811.2179995514
45478
45140
200
font/woff2
Font
https://www.playalinda.com/static/Moderat-Regular-4e8d052625725e08388fc0bd439d72bb.woff2
h2
1089.1619999893
1458.5949997418
46038
45700
200
font/woff2
Font
https://www.playalinda.com/static/Canela-Light-d23ac72def0e402a2850ffc6d02c48eb.woff2
h2
1089.3549998291
1582.2089998983
41190
40852
200
font/woff2
Font
https://www.playalinda.com/static/Moderat-Bold-d7ca051fc2659c4ebefc0632e6ca2661.woff2
h2
1090.1809995994
1521.3329996914
45814
45476
200
font/woff2
Font
https://www.playalinda.com/static/Canela-LightItalic-51c7a894870ae4060dc90fe588355d8f.woff2
h2
1090.744999703
1520.5559995957
45246
44908
200
font/woff2
Font
https://playa-linda.cdn.prismic.io/playa-linda/7e9ec99e-f24b-487a-90c8-c89e3084c46f_video_02.mp4
h2
1118.9449997619
1788.6089999229
4922775
3145728
206
video/mp4
Media
data
1122.8779996745
1122.9519997723
0
108
200
image/png
Image
data
1123.3799997717
1123.5339995474
0
3899
200
image/png
Image
data
1123.8439995795
1123.9489996806
0
4247
200
image/png
Image
data
1124.2309999652
1124.3389998563
0
4195
200
image/png
Image
data
1124.6689995751
1124.7899997979
0
5915
200
image/png
Image
data
1125.2949996851
1125.4489999264
0
7365
200
image/png
Image
https://www.googletagmanager.com/gtag/js?id=G-4QN5YK62LF
h2
1132.1019995958
1154.9139996059
44569
109095
200
application/javascript
Script
data
1149.3109995499
1149.5149997063
0
6676
200
image/png
Image
https://api.openweathermap.org/data/2.5/weather?q=Aruba&units=metric&appid=7114db25bf0d00e09a4cda9c7a388b0d
http/1.1
1914.40399969
2131.1439997517
798
465
200
application/json
Fetch
https://images.prismic.io/playa-linda/57af7405-50ef-4546-8226-ff1c1fae3b4f_playa_linda_logo.png?auto=compress%2Cformat&w=162&h=49&dpr=1
h2
1933.2659998909
1999.7949996032
3954
3410
200
image/webp
Image
https://images.prismic.io/playa-linda/3bba3d00-f4a6-4f52-a86d-269394606b66_Asset+5.png?auto=compress%2Cformat&rect=0%2C2%2C65%2C27&w=45&h=19&dpr=1
h2
1933.420999907
2003.502999898
1109
612
200
image/webp
Image
https://images.prismic.io/playa-linda/825b618f-6414-4dfa-b9f8-18f8c063d982_Activities3.png?auto=compress%2Cformat&w=45&h=45&dpr=1
h2
1933.6579996161
2015.540999826
1686
1188
200
image/webp
Image
https://images.prismic.io/playa-linda/71dc491b-ef3b-4264-ab78-b2787375589d_Asset+2.png?auto=compress%2Cformat&rect=0%2C0%2C41%2C31&w=45&h=34&dpr=1
h2
1933.8739998639
1992.2349997796
1558
1060
200
image/webp
Image
https://images.prismic.io/playa-linda/91a6b8be-2458-480d-8aa0-84b549a35078_Asset+3.png?auto=compress%2Cformat&rect=0%2C0%2C45%2C45&w=45&h=45&dpr=1
h2
1934.0959996916
2004.2769997381
1178
680
200
image/webp
Image
https://images.prismic.io/playa-linda/8f2e37bd-a09a-4442-aa0e-48332786f19a_Asset+4.png?auto=compress%2Cformat&w=45&h=45&dpr=1
h2
1934.4789995812
2003.9419997483
859
362
200
image/webp
Image
https://www.playalinda.com/page-data/rooms/page-data.json
h2
1950.7599999197
2027.8699998744
540
0
200
application/json
Other
https://www.playalinda.com/page-data/timeshare-overview/page-data.json
h2
1969.4339996204
2112.4069998041
2936
0
200
application/json
Other
https://www.playalinda.com/page-data/amenities/page-data.json
h2
1970.0909997337
2090.0519997813
547
0
200
application/json
Other
https://www.google-analytics.com/g/collect?v=2&tid=G-4QN5YK62LF&gtm=2oe840&_p=1256333224&sr=800x600&ul=en-us&cid=1917656303.1628540575&_s=1&dl=https%3A%2F%2Fwww.playalinda.com%2F&dt=Playa%20Linda%20%7C%20Home&sid=1628540574&sct=1&seg=0&en=page_view&_fv=1&_nsi=1&_ss=1&ep.page_path=%2F
1978.7289998494
1993.2349999435
0
0
-1
Ping
https://www.playalinda.com/page-data/rooms/page-data.json
h2
2035.7709997334
2195.3989998437
540
198
200
application/json
XHR
https://www.playalinda.com/page-data/amenities/page-data.json
h2
2093.3909998275
2171.6439998709
547
205
200
application/json
XHR
https://www.playalinda.com/page-data/timeshare-overview/page-data.json
h2
2114.8029998876
2253.0009998009
2935
11450
200
application/json
XHR
https://www.playalinda.com/component---src-pages-amenities-tsx-70a0add5228c0a48ea4a.js
h2
2175.0369998626
2317.2849998809
3053
0
200
application/javascript
Other
https://www.playalinda.com/component---src-pages-rooms-tsx-f8a8a7c4ed3594ab4a2c.js
h2
2197.9599995539
2334.5999997109
3084
0
200
application/javascript
Other
https://www.playalinda.com/component---src-components-templates-content-page-tsx-6ff79bb89f81e383ed61.js
h2
2255.9940000065
2338.1049996242
4664
0
200
application/javascript
Other
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)
1045.557
7.879
1054.364
8.849
1063.463
19.506
1082.989
27.883
1115.452
8.747
1126.241
6.07
1134.568
19.763
1174.418
11.542
1186.335
11.271
1222.215
9.948
1477.953
80.13
1558.108
11.3
1586.422
10.671
1602.425
7.924
1610.492
57.544
1668.078
6.985
1773.927
157.098
1931.05
9.194
1949.362
26.624
1976.019
21.487
2020.632
16.071
2138.867
8.399
2347.934
5.397
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Playalinda.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Playalinda.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Playalinda.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Playalinda.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Playalinda.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Playalinda.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 460 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://www.playalinda.com/
460.072
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Playalinda.com 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 0 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://www.playalinda.com/f143af7d537af45a50ebbb3b8b4b7a28bb3023a8-e852cd01c0d35bf5790b.js
61
https://www.playalinda.com/app-8d572199f93af02e0d57.js
54
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 595 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.playalinda.com/commons-119a607f4be1340eaf26.js
88134
https://www.playalinda.com/app-8d572199f93af02e0d57.js
71520
https://www.playalinda.com/static/Moderat-Regular-4e8d052625725e08388fc0bd439d72bb.woff2
46038
https://www.playalinda.com/
45819
https://www.playalinda.com/static/Moderat-Bold-d7ca051fc2659c4ebefc0632e6ca2661.woff2
45814
https://www.playalinda.com/static/Moderat-Medium-70a70082030b96d40bfa454c1a49243f.woff2
45478
https://www.playalinda.com/static/Canela-LightItalic-51c7a894870ae4060dc90fe588355d8f.woff2
45246
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js
45109
https://www.googletagmanager.com/gtag/js?id=G-4QN5YK62LF
44569
https://www.playalinda.com/static/Canela-Light-d23ac72def0e402a2850ffc6d02c48eb.woff2
41190
Uses efficient cache policy on static assets — 0 resources found
Playalinda.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoids an excessive DOM size — 401 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
401
Maximum DOM Depth
path
15
Maximum Child Elements
body
15
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Playalinda.com 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 — 1 user timing
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
onInitialClientRender
Mark
1915.693
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js
281.459
250.891
3.21
https://www.playalinda.com/
174.179
7.28
1.654
Unattributable
109.742
10.967
0.172
https://www.playalinda.com/commons-119a607f4be1340eaf26.js
78.263
67.336
6.269
Minimizes main-thread work — 0.7 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
380.165
Other
157.426
Style & Layout
82.192
Rendering
46.871
Script Parsing & Compilation
25.219
Parse HTML & CSS
24.385
Garbage Collection
2.866
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 • 5,403 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
5532377
Media
1
4922775
Script
11
269843
Font
5
223766
Other
21
59830
Document
1
45819
Image
6
10344
Stylesheet
0
0
Third-party
10
4978486
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
44569
0
SHOW DETAILS
0
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
resort logo
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
Vacation Ownership
1.2333284081954E-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 — 3 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://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js
1610
157
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js
1130
80
https://www.playalinda.com/commons-119a607f4be1340eaf26.js
1450
58
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.

Metrics

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

Other

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

Opportunities

Reduce unused JavaScript — Potential savings of 91 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://www.playalinda.com/commons-119a607f4be1340eaf26.js
88134
40165
https://www.playalinda.com/app-8d572199f93af02e0d57.js
71520
31618
https://www.googletagmanager.com/gtag/js?id=G-4QN5YK62LF
44569
20934
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Playalinda.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://playalinda.com/
190
https://playalinda.com/
150
https://www.playalinda.com/
0

Metrics

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

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of playalinda.com. 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.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[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"]`
Playalinda.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that playalinda.com 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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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
Gatsby
core-js
core-js-global@3.12.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.playalinda.com/commons-119a607f4be1340eaf26.js
https://www.playalinda.com/commons-119a607f4be1340eaf26.js.map
https://www.playalinda.com/app-8d572199f93af02e0d57.js
https://www.playalinda.com/app-8d572199f93af02e0d57.js.map
https://www.playalinda.com/1bfc9850-4f063d657ae861026224.js
https://www.playalinda.com/1bfc9850-4f063d657ae861026224.js.map
https://www.playalinda.com/webpack-runtime-ec4ba749219663bc2f8f.js
https://www.playalinda.com/webpack-runtime-ec4ba749219663bc2f8f.js.map
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js.map
https://www.playalinda.com/f143af7d537af45a50ebbb3b8b4b7a28bb3023a8-e852cd01c0d35bf5790b.js
https://www.playalinda.com/f143af7d537af45a50ebbb3b8b4b7a28bb3023a8-e852cd01c0d35bf5790b.js.map
https://www.playalinda.com/d7eeaac4-9008aa8b67b154adcf61.js
https://www.playalinda.com/d7eeaac4-9008aa8b67b154adcf61.js.map
https://www.playalinda.com/component---src-pages-index-tsx-aba1639435ce1c619a8f.js
https://www.playalinda.com/component---src-pages-index-tsx-aba1639435ce1c619a8f.js.map
https://www.playalinda.com/17007de1-558c070d1c7666980cdb.js
https://www.playalinda.com/17007de1-558c070d1c7666980cdb.js.map
https://www.playalinda.com/0c428ae2-86697eaead34d26e7ff5.js
https://www.playalinda.com/0c428ae2-86697eaead34d26e7ff5.js.map
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://playalinda.com/
Allowed
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for playalinda.com. 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 playalinda.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

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

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 playalinda.com. 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.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
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 playalinda.com 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.
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) 82
Performance 43
Accessibility 100
Best Practices 93
SEO 98
Progressive Web App 75
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.playalinda.com/
Updated: 9th August, 2021

1.25 seconds
First Contentful Paint (FCP)
92%
6%
2%

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

Simulate loading on mobile
43

Performance

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

Metrics

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

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Playalinda.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Playalinda.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Playalinda.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Playalinda.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Playalinda.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Playalinda.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 210 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://www.playalinda.com/
213.06
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Playalinda.com 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 0 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://www.playalinda.com/f143af7d537af45a50ebbb3b8b4b7a28bb3023a8-e852cd01c0d35bf5790b.js
61
https://www.playalinda.com/app-8d572199f93af02e0d57.js
54
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 588 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.playalinda.com/commons-119a607f4be1340eaf26.js
88134
https://www.playalinda.com/app-8d572199f93af02e0d57.js
71520
https://www.playalinda.com/static/Moderat-Regular-4e8d052625725e08388fc0bd439d72bb.woff2
46038
https://www.playalinda.com/
45819
https://www.playalinda.com/static/Moderat-Bold-d7ca051fc2659c4ebefc0632e6ca2661.woff2
45813
https://www.playalinda.com/static/Moderat-Medium-70a70082030b96d40bfa454c1a49243f.woff2
45477
https://www.playalinda.com/static/Canela-LightItalic-51c7a894870ae4060dc90fe588355d8f.woff2
45246
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js
45109
https://www.googletagmanager.com/gtag/js?id=G-4QN5YK62LF
44568
https://www.playalinda.com/static/Canela-Light-d23ac72def0e402a2850ffc6d02c48eb.woff2
41190
Uses efficient cache policy on static assets — 0 resources found
Playalinda.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoids an excessive DOM size — 401 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
401
Maximum DOM Depth
path
15
Maximum Child Elements
body
15
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Playalinda.com 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 — 1 user timing
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
onInitialClientRender
Mark
1023.108
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 — 35 requests • 5,395 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
35
5524789
Media
1
4922783
Script
11
269842
Font
5
223764
Document
1
45819
Other
12
41210
Image
5
21371
Stylesheet
0
0
Third-party
9
4989520
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
44568
0
SHOW DETAILS
0
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
resort logo
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
svg
0.00012885199652778
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 — 9 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://www.playalinda.com/commons-119a607f4be1340eaf26.js
6335
609
https://www.playalinda.com/app-8d572199f93af02e0d57.js
5040
433
https://www.playalinda.com/commons-119a607f4be1340eaf26.js
6090
245
https://www.playalinda.com/
2190
110
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js
5473
92
https://www.playalinda.com/app-8d572199f93af02e0d57.js
6944
88
https://www.playalinda.com/
2300
74
Unattributable
2374
62
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js
4590
52
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://playalinda.com/
http/1.1
0
106.10699979588
324
0
301
text/plain
https://playalinda.com/
http/1.1
106.90800007433
185.61400007457
376
0
301
text/plain
https://www.playalinda.com/
h2
186.33199995384
398.39500002563
45819
146332
200
text/html
Document
https://www.playalinda.com/webpack-runtime-ec4ba749219663bc2f8f.js
h2
417.01600002125
499.15599962696
3026
5380
200
application/javascript
Script
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js
h2
417.54499962553
500.13599963859
45109
148224
200
application/javascript
Script
https://www.playalinda.com/app-8d572199f93af02e0d57.js
h2
417.8059999831
628.74699989334
71520
312666
200
application/javascript
Script
https://www.playalinda.com/1bfc9850-4f063d657ae861026224.js
h2
418.06599963456
498.57899965718
1219
856
200
application/javascript
Script
https://www.playalinda.com/d7eeaac4-9008aa8b67b154adcf61.js
h2
418.58199983835
499.55399986356
1024
661
200
application/javascript
Script
https://www.playalinda.com/0c428ae2-86697eaead34d26e7ff5.js
h2
418.96999999881
623.07399976999
1220
2747
200
application/javascript
Script
https://www.playalinda.com/17007de1-558c070d1c7666980cdb.js
h2
419.24799978733
500.83899963647
1092
729
200
application/javascript
Script
https://www.playalinda.com/commons-119a607f4be1340eaf26.js
h2
419.58699980751
769.6940000169
88134
316685
200
application/javascript
Script
https://www.playalinda.com/f143af7d537af45a50ebbb3b8b4b7a28bb3023a8-e852cd01c0d35bf5790b.js
h2
419.8539997451
501.63899967447
5873
16012
200
application/javascript
Script
https://www.playalinda.com/component---src-pages-index-tsx-aba1639435ce1c619a8f.js
h2
420.1489998959
623.73799970374
7057
23125
200
application/javascript
Script
https://www.playalinda.com/page-data/index/page-data.json
h2
420.74199998751
623.45599988475
534
192
200
application/json
Other
https://www.playalinda.com/page-data/sq/d/1001606710.json
h2
421.18999967352
502.01399996877
3445
14238
200
application/json
Other
https://www.playalinda.com/page-data/sq/d/2686767999.json
h2
421.75599979237
551.99899990112
2069
9736
200
application/json
Other
https://www.playalinda.com/page-data/sq/d/379716309.json
h2
422.0619997941
626.96999963373
31504
51084
200
application/json
Other
https://www.playalinda.com/page-data/sq/d/3841368162.json
h2
422.26299969479
624.33699984103
876
1465
200
application/json
Other
https://www.playalinda.com/page-data/sq/d/4229546192.json
h2
422.60699998587
683.12099995092
432
91
200
application/json
Other
https://www.playalinda.com/page-data/sq/d/63159454.json
h2
422.90399968624
501.18299992755
461
119
200
application/json
Other
https://www.playalinda.com/page-data/app-data.json
h2
423.25800005347
550.23499997333
391
50
200
application/json
Other
https://www.playalinda.com/static/Moderat-Regular-4e8d052625725e08388fc0bd439d72bb.woff2
h2
466.2329996936
624.95499989018
46038
45700
200
font/woff2
Font
https://www.playalinda.com/static/Canela-Light-d23ac72def0e402a2850ffc6d02c48eb.woff2
h2
470.67900002003
560.63399976119
41190
40852
200
font/woff2
Font
https://www.playalinda.com/static/Moderat-Bold-d7ca051fc2659c4ebefc0632e6ca2661.woff2
h2
471.26800008118
683.87799989432
45813
45476
200
font/woff2
Font
https://www.playalinda.com/static/Moderat-Medium-70a70082030b96d40bfa454c1a49243f.woff2
h2
472.06099983305
684.67999994755
45477
45140
200
font/woff2
Font
https://www.playalinda.com/static/Canela-LightItalic-51c7a894870ae4060dc90fe588355d8f.woff2
h2
472.30499982834
559.88999968395
45246
44908
200
font/woff2
Font
https://playa-linda.cdn.prismic.io/playa-linda/7e9ec99e-f24b-487a-90c8-c89e3084c46f_video_02.mp4
h2
508.38600005955
760.35800017416
4922783
3145728
206
video/mp4
Media
data
512.6600000076
512.73499988019
0
108
200
image/png
Image
data
513.16299987957
513.28899990767
0
3899
200
image/png
Image
data
513.59599968418
513.70000001043
0
4247
200
image/png
Image
data
513.97999981418
514.12599999458
0
4195
200
image/png
Image
data
514.57899995148
514.71999986097
0
5915
200
image/png
Image
data
515.1430000551
515.33099962398
0
7365
200
image/png
Image
https://www.googletagmanager.com/gtag/js?id=G-4QN5YK62LF
h2
523.5279998742
557.8979998827
44568
109095
200
application/javascript
Script
data
547.37899964675
547.57099971175
0
6676
200
image/png
Image
https://api.openweathermap.org/data/2.5/weather?q=Aruba&units=metric&appid=7114db25bf0d00e09a4cda9c7a388b0d
http/1.1
1021.5670000762
1214.3239998259
798
465
200
application/json
Fetch
https://images.prismic.io/playa-linda/57af7405-50ef-4546-8226-ff1c1fae3b4f_playa_linda_logo.png?auto=compress%2Cformat&w=162&h=49&dpr=2
h2
1038.2739999332
1056.452000048
10188
9690
200
image/webp
Image
https://images.prismic.io/playa-linda/3bba3d00-f4a6-4f52-a86d-269394606b66_Asset+5.png?auto=compress%2Cformat&rect=0%2C2%2C65%2C27&w=45&h=19&dpr=2
h2
1038.4519998915
1055.9229999781
1481
984
200
image/webp
Image
https://images.prismic.io/playa-linda/825b618f-6414-4dfa-b9f8-18f8c063d982_Activities3.png?auto=compress%2Cformat&w=45&h=45&dpr=2
h2
1038.7069997378
1057.6369999908
1848
1350
200
image/webp
Image
https://images.prismic.io/playa-linda/71dc491b-ef3b-4264-ab78-b2787375589d_Asset+2.png?auto=compress%2Cformat&rect=0%2C0%2C41%2C31&w=45&h=34&dpr=2
h2
1038.9469997026
1057.4260000139
3568
3070
200
image/webp
Image
https://images.prismic.io/playa-linda/91a6b8be-2458-480d-8aa0-84b549a35078_Asset+3.png?auto=compress%2Cformat&rect=0%2C0%2C45%2C45&w=45&h=45&dpr=2
h2
1039.2819996923
1057.1339996532
4286
3788
200
image/webp
Image
https://www.google-analytics.com/g/collect?v=2&tid=G-4QN5YK62LF&gtm=2oe840&_p=1796435559&sr=360x640&ul=en-us&cid=1234443829.1628540596&_s=1&dl=https%3A%2F%2Fwww.playalinda.com%2F&dt=Playa%20Linda%20%7C%20Home&sid=1628540596&sct=1&seg=0&en=page_view&_fv=1&_nsi=1&_ss=1&ep.page_path=%2F
1078.0059997924
1095.4309999943
0
0
-1
Ping
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)
418.499
9.721
429.066
8.742
438.074
27.558
465.69
36.841
506.738
15.444
524.31
6.266
536.725
23.588
579.361
10.059
593.416
11.546
605.045
16.392
621.45
11.529
640.872
5.375
652.515
12.515
665.351
108.332
774.63
5.539
780.187
5.021
785.703
9.508
821.216
61.185
882.47
7.652
892.47
152.261
1044.789
8.577
1058.409
21.881
1080.437
23.069
1119.268
13.122
1230.65
9.904
1419.261
5.41
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 2.4 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 4.9 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 6.8 s
The time taken for the page to become fully interactive.

Other

First Meaningful Paint — 2.4 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 4474 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Reduce unused JavaScript — Potential savings of 91 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://www.playalinda.com/commons-119a607f4be1340eaf26.js
88134
40165
https://www.playalinda.com/app-8d572199f93af02e0d57.js
71520
31978
https://www.googletagmanager.com/gtag/js?id=G-4QN5YK62LF
44568
20934

Diagnostics

Reduce JavaScript execution time — 1.6 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://www.playalinda.com/commons-119a607f4be1340eaf26.js
933.592
861.576
21.44
https://www.playalinda.com/
791.796
28.352
6.788
https://www.playalinda.com/app-8d572199f93af02e0d57.js
509.908
451.292
23.8
Unattributable
489.116
52.944
0.86
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js
166.572
53.752
10.948
https://www.googletagmanager.com/gtag/js?id=G-4QN5YK62LF
102.392
84.224
12.364
Minimize main-thread work — 3.0 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
1543.496
Other
667.656
Style & Layout
392.9
Rendering
170.748
Parse HTML & CSS
128.232
Script Parsing & Compilation
93.568
Garbage Collection
43.632

Metrics

Largest Contentful Paint — 7.5 s
The timing of the largest text or image that is painted.
Total Blocking Time — 1,030 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

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

Opportunities

Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Playalinda.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://playalinda.com/
630
https://playalinda.com/
480
https://www.playalinda.com/
0
100

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of playalinda.com. 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.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[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"]`
Playalinda.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that playalinda.com 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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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
Gatsby
core-js
core-js-global@3.12.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.playalinda.com/commons-119a607f4be1340eaf26.js
https://www.playalinda.com/commons-119a607f4be1340eaf26.js.map
https://www.playalinda.com/1bfc9850-4f063d657ae861026224.js
https://www.playalinda.com/1bfc9850-4f063d657ae861026224.js.map
https://www.playalinda.com/webpack-runtime-ec4ba749219663bc2f8f.js
https://www.playalinda.com/webpack-runtime-ec4ba749219663bc2f8f.js.map
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js
https://www.playalinda.com/framework-0d1647dcd711d5a17ca0.js.map
https://www.playalinda.com/f143af7d537af45a50ebbb3b8b4b7a28bb3023a8-e852cd01c0d35bf5790b.js
https://www.playalinda.com/f143af7d537af45a50ebbb3b8b4b7a28bb3023a8-e852cd01c0d35bf5790b.js.map
https://www.playalinda.com/d7eeaac4-9008aa8b67b154adcf61.js
https://www.playalinda.com/d7eeaac4-9008aa8b67b154adcf61.js.map
https://www.playalinda.com/component---src-pages-index-tsx-aba1639435ce1c619a8f.js
https://www.playalinda.com/component---src-pages-index-tsx-aba1639435ce1c619a8f.js.map
https://www.playalinda.com/app-8d572199f93af02e0d57.js
https://www.playalinda.com/app-8d572199f93af02e0d57.js.map
https://www.playalinda.com/17007de1-558c070d1c7666980cdb.js
https://www.playalinda.com/17007de1-558c070d1c7666980cdb.js.map
https://www.playalinda.com/0c428ae2-86697eaead34d26e7ff5.js
https://www.playalinda.com/0c428ae2-86697eaead34d26e7ff5.js.map
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://playalinda.com/
Allowed
98

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for playalinda.com. 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 playalinda.com on mobile screens.
Document uses legible font sizes — 100% 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
SHOW DETAILS
100.00%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 91% 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.
Tap Target Size Overlapping Target
FAQ
26x33
Careers
About
39x33
Awards

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 playalinda.com. 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.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
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
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 playalinda.com 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.
Content is not 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.
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: 75.2.60.5
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
Everyones Internet, LLC dba SoftLayer 66.228.119.70
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: playalinda.com
Issued By: R3
Valid From: 14th July, 2021
Valid To: 12th October, 2021
Subject: CN = playalinda.com
Hash: 8f056c63
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x044B84ECEF30F59F7E3CA6488EAE5FCEEA38
Serial Number (Hex): 044B84ECEF30F59F7E3CA6488EAE5FCEEA38
Valid From: 14th July, 2024
Valid To: 12th October, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org
Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/
SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Jul 14 10:42:20.360 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:84:80:35:7D:AC:34:D1:DC:AD:76:8D:
79:FD:FF:46:C0:16:4B:9A:65:E3:D8:AF:45:B6:25:9C:
1C:FB:5E:F1:FD:02:20:09:A4:12:71:55:D0:2B:22:8F:
AE:4E:03:1F:08:F4:2C:D8:70:21:3C:A7:9A:F4:80:6B:
12:37:FF:04:D9:16:5A
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Jul 14 10:42:20.393 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:1F:27:59:ED:31:2D:AF:79:0C:47:78:C7:
01:B1:84:AF:78:D0:65:94:D5:F2:3A:E4:6D:89:D5:20:
A4:71:D6:32:02:20:01:89:EC:0D:BF:C0:85:8D:7C:BC:
E1:BD:1A:F7:15:4E:F9:18:50:B9:9A:2E:10:20:8C:57:
97:AB:F1:78:02:4A
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.playalinda.com
DNS:playalinda.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
playalinda.com. 75.2.60.5 IN 899

NS Records

Host Nameserver Class TTL
playalinda.com. ns1.softlayer.com. IN 899
playalinda.com. ns2.softlayer.com. IN 899

MX Records

Priority Host Server Class TTL
10 playalinda.com. email.playalinda.com. IN 899

SOA Records

Domain Name Primary NS Responsible Email TTL
playalinda.com. ns1.softlayer.com. root.playalinda.com. 899

TXT Records

Host Value Class TTL
playalinda.com. v=spf1 IN 899

HTTP Response Headers

HTTP-Code: HTTP/1.1 301 Moved Permanently
cache-control: public, max-age=0, must-revalidate
content-type: text/plain
date: 9th August, 2021
server: Netlify
content-length: 38
x-nf-request-id: 01FCP99XK2ZRS8QRJPDZCJ3XHM
location: https://playalinda.com/
age: 6526

Whois Lookup

Created: 19th September, 1997
Changed: 24th June, 2021
Expires: 18th September, 2022
Registrar: Everyones Internet, LLC dba SoftLayer
Status: clientTransferProhibited
clientUpdateProhibited
Nameservers: ns1.softlayer.com
ns2.softlayer.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: REDACTED FOR PRIVACY
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: OT
Owner Country: AW
Owner Phone: REDACTED FOR PRIVACY
Owner Email: https://tieredaccess.com/contact/b0aded10-cbe3-4521-88ae-69ed0afef8fa
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY
Full Whois: Domain Name: PLAYALINDA.COM
Registry Domain ID: 483520_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.softlayer.com
Registrar URL: http://www.softlayer.com
Updated Date: 2021-06-24T13:16:29
Creation Date: 1997-09-19T04:00:00
Registrar Registration Expiration Date: 2022-09-18T04:00:00
Registrar: Everyones Internet, LLC dba SoftLayer
Registrar IANA ID: 925
Reseller: SoftLayer
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID:
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: OT
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: AW
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext:
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext:
Registrant Email: https://tieredaccess.com/contact/b0aded10-cbe3-4521-88ae-69ed0afef8fa
Registry Admin ID:
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext:
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext:
Admin Email: REDACTED FOR PRIVACY
Registry Tech ID:
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext:
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext:
Tech Email: REDACTED FOR PRIVACY
Name Server: ns2.softlayer.com
Name Server: ns1.softlayer.com
DNSSEC: unsigned
Registrar Abuse Contact Email: abuse@softlayer.com
Registrar Abuse Contact Phone: +1.2144420600
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-08-09T20:22:49Z <<<

"For more information on Whois status codes, please visit https://icann.org/epp"

Registration Service Provider:
SoftLayer, domains@softlayer.com
+1.2144420600x43148
http://www.softlayer.com
This company may be contacted for domain login/passwords,
DNS/Nameserver changes, and general domain support questions.

The Data in the ResellOne Registrar WHOIS database is provided to you by ResellOne
for information purposes only, and may be used to assist you in obtaining
information about or related to a domain name's registration record.

ResellOne makes this information available "as is," and does not guarantee its accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
a) allow, enable, or otherwise support the transmission by e-mail,
telephone, or facsimile of mass, unsolicited, commercial advertising or
solicitations to entities other than the data recipient's own existing
customers; or (b) enable high volume, automated, electronic processes that
send queries or data to the systems of any Registry Operator or
ICANN-Accredited registrar, except as reasonably necessary to register
domain names or modify existing registrations.

The compilation, repackaging, dissemination or other use of this Data is
expressly prohibited without the prior written consent of ResellOne.

ResellOne reserves the right to terminate your access to the ResellOne WHOIS
database in its sole discretion, including without limitation, for excessive
querying of the WHOIS database or for failure to otherwise abide by this policy.

ResellOne reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by these terms.

NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY. LACK OF A DOMAIN
RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.
View Raw Whois

Nameservers

Name IP Address
ns1.softlayer.com 67.228.254.4
ns2.softlayer.com 67.228.255.5
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
aruba-manchebo.com
0/5
aruba.hyatt.com
0/5
arubagrand.com
0/5
arubaonline.com
0/5
arubarenaissance.com
0/5
All sites similar to playalinda.com

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
cardsagainsthumanity.com
$6,091 USD 3/5
lofficiel.in
$632 USD 1/5
rockthebells.com
$4,441 USD 2/5
vranimesociety.com
0/5
Love W3 Snoop?
Update Now

playalinda.com Infographic

playalinda.com by the numbers infographic

Recently Updated

dibamoviez.com
steklomaster.kz
kooracity.com
matchdz.com
o2tvseries.co.za
thesouledstore.com
giornalesentire.it
my4u.com
overlay.co
overlays.co

Recently Viewed

vbaf.com
wwbinhinsi.com
wwbinhindi.com
vstartek.com
josepika.com
gezondenzo.net
matamsa.org
romaselectroengineering.com
dskjewelry.com
adamvaughan.org