meetflings.com

meetflings.com is SSL secured

Free website and domain report on meetflings.com

Last Updated: 21st February, 2023 Update Now
Overview

Snoop Summary for meetflings.com

This is a free and comprehensive report about meetflings.com. The domain meetflings.com is currently hosted on a server located in Mountain View, California in United States with the IP address 35.203.113.247, where the local currency is USD and English is the local language. Our records indicate that meetflings.com is privately registered by Privacy service provided by Withheld for Privacy ehf. Meetflings.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If meetflings.com was to be sold it would possibly be worth $865 USD (based on the daily revenue potential of the website over a 24 month period). Meetflings.com is somewhat popular with an estimated 411 daily unique visitors. This report was last updated 21st February, 2023.

About meetflings.com

Site Preview: meetflings.com meetflings.com
Title: MeetFlings- Have an affair tonight!
Description: Find a no-strings-attached relationship tonight.
Keywords and Tags: affair, cheaters, dating, personals, spam urls
Related Terms: 20 20 tonight, cbs schedule tonight, cheat tonight, dogging tonight, find an affair, is it going to rain tonight, lady hear me tonight, muppets tonight, new on tv tonight, wonderful tonight acoustic karaoke
Fav Icon:
Age: Over 2 years old
Domain Created: 19th November, 2021
Domain Updated: 27th October, 2022
Domain Expires: 19th November, 2023
Review

Snoop Score

1/5

Valuation

$865 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,654,570
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 6
Moz Page Authority: 17

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 411
Monthly Visitors: 12,510
Yearly Visitors: 150,015
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

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

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 64
Performance 93
Accessibility 78
Best Practices 75
SEO 73
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.meetflings.com
Updated: 20th March, 2022

3.95 seconds
First Contentful Paint (FCP)
49%
21%
30%

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

Simulate loading on desktop
93

Performance

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

Metrics

Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 1.2 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.011
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
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://meetflings.com/
http/1.1
0
204.13800003007
159
0
301
text/plain
https://meetflings.com/
http/1.1
204.47100000456
524.92200001143
441
0
302
text/html
https://www.meetflings.com/index.php
h2
525.23299999302
953.50699999835
18424
82555
200
text/html
Document
https://fonts.googleapis.com/css?family=Catamaran&display=swap
h2
965.04999999888
973.59499998856
1217
1107
200
text/css
Stylesheet
https://use.fontawesome.com/releases/v5.4.1/css/all.css
h2
965.19300004002
1014.5280000288
11908
50397
200
text/css
Stylesheet
https://www.meetflings.com/css/jquery/jquery-ui.css
h2
965.46400000807
1118.8679999905
10055
35298
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=Open+Sans:wght@400;600;700;800&family=Roboto:wght@400;700&display=swap
h2
965.74600000167
997.44400003692
1736
15816
200
text/css
Stylesheet
https://www.meetflings.com/js/jquery.min.js
h2
966.22500004014
1375.6799999974
36095
88151
200
application/javascript
Script
https://www.meetflings.com/js/jquery-ui.min.js
h2
966.48300002562
1443.2350000134
80696
243603
200
application/javascript
Script
https://www.meetflings.com/js/jquery.emailverifyservice.js
h2
966.8890000321
1112.2109999997
979
2249
200
application/javascript
Script
https://www.meetflings.com/js/jquery.usernameverifyservice.js
h2
967.16200001538
1243.5050000204
828
1324
200
application/javascript
Script
https://www.meetflings.com/js/join/jquery.formValidation.js
h2
967.53700001864
1310.5729999952
4579
23602
200
application/javascript
Script
https://www.meetflings.com/js/landing_pages/footerLinks.js?version=599e2555d
h2
967.83300000243
1113.0920000141
1203
2816
200
application/javascript
Script
https://www.meetflings.com/js/jquery.location_list.js?version=599e2555d
h2
968.21800002363
1112.6689999946
3044
12951
200
application/javascript
Script
https://www.meetflings.com/js/join/modern/formValidation.js?version=599e2555d
h2
968.58600003179
1286.0840000212
1762
6859
200
application/javascript
Script
https://www.meetflings.com/js/join/modern/modernFormValidation.js?version=599e2555d
h2
968.87500002049
1365.243999986
4668
26180
200
application/javascript
Script
https://notifybrowser.com/webpush.js
h2
969.16700003203
1071.2129999883
2390
3526
200
application/javascript
Script
https://www.meetflings.com/js/push-notifications.js
h2
969.38399999635
1308.6190000176
1689
4795
200
application/javascript
Script
https://www.meetflings.com/js/ads.js?adids=1&banner_id=1
h2
969.88500002772
1115.3850000119
470
118
200
application/javascript
Script
https://www.meetflings.com/js/aiCont.js
h2
970.1730000088
1133.9210000006
1013
2079
200
application/javascript
Script
https://www.meetflings.com/libs/templates/default/components_new/push_notifications/img/feb_22_v1_nude.gif
h2
1384.3970000162
1720.4930000007
658569
658229
200
image/gif
Image
https://www.meetflings.com/images/whitelabel/64374/landing_pages/logo_57.png
h2
1458.6070000078
1598.1369999936
4835
4553
200
image/png
Image
https://www.meetflings.com/images/whitelabel/64374/landing_pages/305/img/2/body.jpg
h2
1511.164000025
1722.8510000277
445500
445214
200
image/jpeg
Image
https://fonts.gstatic.com/s/opensans/v28/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
h2
1514.5660000271
1519.1089999862
40484
39556
200
font/woff2
Font
https://use.fontawesome.com/releases/v5.4.1/webfonts/fa-solid-900.woff2
h2
1517.3320000176
1694.8700000066
73120
72000
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1518.3970000362
1522.5550000323
11976
11048
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v29/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1518.647000019
1522.1449999954
11960
11032
200
font/woff2
Font
https://use.fontawesome.com/releases/v5.4.1/webfonts/fa-regular-400.woff2
h2
1519.6069999947
1562.1570000076
16009
14880
200
font/woff2
Font
https://www.meetflings.com/includes/ajax_location_list.php
h2
1601.7930000089
1724.0020000027
487
74
200
text/html
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)
997.062
6.517
1004.248
7.993
1424.533
20.1
1497.939
44.425
1542.389
48.761
1591.777
6.366
1605.804
14.455
1621.612
21.205
1642.833
8.073
1656.092
6.274
1736.411
6.959
1743.75
5.512
1766.187
7.23
1779.959
102.735
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Meetflings.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Meetflings.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 5 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Meetflings.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.meetflings.com/js/join/jquery.formValidation.js
4579
3035
https://www.meetflings.com/js/join/modern/modernFormValidation.js?version=599e2555d
4668
2246
Reduce unused CSS — Potential savings of 11 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Meetflings.com 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://use.fontawesome.com/releases/v5.4.1/css/all.css
11908
11775
Reduce unused JavaScript — Potential savings of 68 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.meetflings.com/js/jquery-ui.min.js
80696
69763
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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 430 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.meetflings.com/index.php
429.268
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Meetflings.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
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://notifybrowser.com/webpush.js
113
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 1,412 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.meetflings.com/libs/templates/default/components_new/push_notifications/img/feb_22_v1_nude.gif
658569
https://www.meetflings.com/images/whitelabel/64374/landing_pages/305/img/2/body.jpg
445500
https://www.meetflings.com/js/jquery-ui.min.js
80696
https://use.fontawesome.com/releases/v5.4.1/webfonts/fa-solid-900.woff2
73120
https://fonts.gstatic.com/s/opensans/v28/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
40484
https://www.meetflings.com/js/jquery.min.js
36095
https://www.meetflings.com/index.php
18424
https://use.fontawesome.com/releases/v5.4.1/webfonts/fa-regular-400.woff2
16009
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
11976
https://fonts.gstatic.com/s/roboto/v29/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
11960
Avoids an excessive DOM size — 384 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
384
Maximum DOM Depth
13
Maximum Child Elements
214
Avoid chaining critical requests — 20 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Meetflings.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
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 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.meetflings.com/index.php
209.078
7.171
2.815
https://www.meetflings.com/js/jquery.min.js
61.42
53.904
2.17
Unattributable
56.997
2.945
0.132
Minimizes main-thread work — 0.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)
Rendering
116.173
Script Evaluation
86.201
Other
70.268
Style & Layout
62.491
Parse HTML & CSS
18.719
Script Parsing & Compilation
12.282
Keep request counts low and transfer sizes small — 29 requests • 1,412 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
29
1446296
Image
3
1108904
Font
5
153549
Script
13
139416
Stylesheet
4
24916
Document
1
18424
Other
3
1087
Media
0
0
Third-party
9
170800
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)
101037
0
67373
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0061275866094621
0.0034709351195167
0.0013079415112512
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 — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.meetflings.com/index.php
192
103
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.2 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.6 s
The time taken for the page contents to be visibly populated.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 560 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Meetflings.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Catamaran&display=swap
1217
230
https://use.fontawesome.com/releases/v5.4.1/css/all.css
11908
270
https://www.meetflings.com/js/jquery.min.js
36095
160
https://www.meetflings.com/js/jquery-ui.min.js
80696
240
https://notifybrowser.com/webpush.js
2390
230
Properly size images — Potential savings of 537 KiB
Images can slow down the page's load time. Meetflings.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.meetflings.com/libs/templates/default/components_new/push_notifications/img/feb_22_v1_nude.gif
658229
549596
Serve images in next-gen formats — Potential savings of 166 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.meetflings.com/images/whitelabel/64374/landing_pages/305/img/2/body.jpg
445214
169733.35
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Meetflings.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://meetflings.com/
190
https://meetflings.com/
150
https://www.meetflings.com/index.php
0
Use video formats for animated content — Potential savings of 444 KiB
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.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.meetflings.com/libs/templates/default/components_new/push_notifications/img/feb_22_v1_nude.gif
658229
454178

Other

Serve static assets with an efficient cache policy — 17 resources found
Meetflings.com 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://www.meetflings.com/libs/templates/default/components_new/push_notifications/img/feb_22_v1_nude.gif
172800000
658569
https://www.meetflings.com/images/whitelabel/64374/landing_pages/305/img/2/body.jpg
172800000
445500
https://www.meetflings.com/js/jquery-ui.min.js
172800000
80696
https://www.meetflings.com/js/jquery.min.js
172800000
36095
https://www.meetflings.com/css/jquery/jquery-ui.css
172800000
10055
https://www.meetflings.com/images/whitelabel/64374/landing_pages/logo_57.png
172800000
4835
https://www.meetflings.com/js/join/modern/modernFormValidation.js?version=599e2555d
172800000
4668
https://www.meetflings.com/js/join/jquery.formValidation.js
172800000
4579
https://www.meetflings.com/js/jquery.location_list.js?version=599e2555d
172800000
3044
https://notifybrowser.com/webpush.js
172800000
2390
https://www.meetflings.com/js/join/modern/formValidation.js?version=599e2555d
172800000
1762
https://www.meetflings.com/js/push-notifications.js
172800000
1689
https://www.meetflings.com/js/landing_pages/footerLinks.js?version=599e2555d
172800000
1203
https://www.meetflings.com/js/aiCont.js
172800000
1013
https://www.meetflings.com/js/jquery.emailverifyservice.js
172800000
979
https://www.meetflings.com/js/jquery.usernameverifyservice.js
172800000
828
https://www.meetflings.com/js/ads.js?adids=1&banner_id=1
172800000
470
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://use.fontawesome.com/releases/v5.4.1/webfonts/fa-solid-900.woff2
177.537999989
https://use.fontawesome.com/releases/v5.4.1/webfonts/fa-regular-400.woff2
42.550000012852
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.meetflings.com/libs/templates/default/components_new/push_notifications/img/feb_22_v1_nude.gif
https://www.meetflings.com/images/whitelabel/64374/landing_pages/logo_57.png
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of meetflings.com on mobile screens.
78

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of meetflings.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.
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.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[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"]`
Meetflings.com 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

Navigation

Heading elements are not 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.
Failing Elements

Internationalization and localization

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
75

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
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

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.4.0
jQuery UI
1.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.
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://meetflings.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
2
Medium
3
High

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
73

SEO

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

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

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of meetflings.com on mobile screens.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

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

PWA

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

PWA Optimized

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.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

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
Does not set 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
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of meetflings.com on mobile screens.
Does not provide 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.
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) 54
Performance 62
Accessibility 78
Best Practices 67
SEO 62
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.meetflings.com
Updated: 20th March, 2022

2.41 seconds
First Contentful Paint (FCP)
60%
22%
18%

0.22 seconds
First Input Delay (FID)
57%
40%
3%

Simulate loading on mobile
62

Performance

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

Metrics

Total Blocking Time — 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).
Cumulative Layout Shift — 0.031
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Meetflings.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Meetflings.com should consider minifying CSS files.
Reduce unused CSS — Potential savings of 11 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Meetflings.com 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://use.fontawesome.com/releases/v5.4.1/css/all.css
11904
11763
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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 170 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.meetflings.com/index.php
170.157
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Meetflings.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://notifybrowser.com/webpush.js
113
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.meetflings.com/images/whitelabel/64374/landing_pages/305/img/2/body.jpg
0
Avoids enormous network payloads — Total size was 796 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.meetflings.com/images/whitelabel/64374/landing_pages/305/img/2/body.jpg
445500
https://www.meetflings.com/js/jquery-ui.min.js
80696
https://use.fontawesome.com/releases/v5.4.1/webfonts/fa-solid-900.woff2
73134
https://fonts.gstatic.com/s/opensans/v28/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
40484
https://www.meetflings.com/libs/templates/default/components_new/push_notifications/img/modal_october_thumb.jpg
39058
https://www.meetflings.com/js/jquery.min.js
36095
https://www.meetflings.com/index.php
18959
https://use.fontawesome.com/releases/v5.4.1/webfonts/fa-regular-400.woff2
15992
https://fonts.gstatic.com/s/roboto/v29/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
11960
https://use.fontawesome.com/releases/v5.4.1/css/all.css
11904
Avoids an excessive DOM size — 388 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
388
Maximum DOM Depth
13
Maximum Child Elements
214
Avoid chaining critical requests — 19 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Meetflings.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
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.meetflings.com/index.php
515.356
21.888
9.096
https://www.meetflings.com/js/jquery.min.js
187.804
161.228
5.752
Unattributable
168.924
14.024
0.708
https://www.meetflings.com/js/jquery-ui.min.js
69.896
55.488
13.88
Minimizes main-thread work — 1.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
261.732
Style & Layout
244.124
Other
228.124
Rendering
155.048
Parse HTML & CSS
58.684
Script Parsing & Compilation
37.092
Keep request counts low and transfer sizes small — 28 requests • 796 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
28
815392
Image
3
489393
Font
4
141570
Script
13
139410
Stylesheet
4
24958
Document
1
18959
Other
3
1102
Media
0
0
Third-party
8
158857
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)
101030
0
55443
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.021163253127254
0.0095551454239217
0.0006315613361451
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 — 4 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.meetflings.com/js/jquery.min.js
4590
186
https://www.meetflings.com/index.php
2040
85
https://www.meetflings.com/js/jquery.min.js
2957
70
https://www.meetflings.com/index.php
638
53
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

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://meetflings.com/
http/1.1
0
135.35399991088
159
0
301
text/plain
https://meetflings.com/
http/1.1
136.15799997933
477.43599978276
456
0
302
text/html
https://www.meetflings.com/index.php
h2
477.74599981494
646.90899988636
18959
85076
200
text/html
Document
https://fonts.googleapis.com/css?family=Catamaran&display=swap
h2
660.05299985409
668.1689999532
1214
1106
200
text/css
Stylesheet
https://use.fontawesome.com/releases/v5.4.1/css/all.css
h2
660.26499983855
698.61799990758
11904
50397
200
text/css
Stylesheet
https://www.meetflings.com/css/jquery/jquery-ui.css
h2
660.58299993165
806.0529998038
10055
35298
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=Open+Sans:wght@400;600;700;800&family=Roboto:wght@400;700&display=swap
h2
660.860999953
668.71399991214
1785
16712
200
text/css
Stylesheet
https://www.meetflings.com/js/jquery.min.js
h2
661.37199988589
884.74699994549
36095
88151
200
application/javascript
Script
https://www.meetflings.com/js/jquery-ui.min.js
h2
661.67799988762
802.40199994296
80696
243603
200
application/javascript
Script
https://www.meetflings.com/js/jquery.emailverifyservice.js
h2
662.12799982168
732.0999999065
979
2249
200
application/javascript
Script
https://www.meetflings.com/js/jquery.usernameverifyservice.js
h2
662.48999978416
884.38299996778
828
1324
200
application/javascript
Script
https://www.meetflings.com/js/join/jquery.formValidation.js
h2
662.75899996981
804.49599982239
4579
23602
200
application/javascript
Script
https://www.meetflings.com/js/landing_pages/footerLinks.js?version=599e2555d
h2
663.11799990945
733.22399985045
1203
2816
200
application/javascript
Script
https://www.meetflings.com/js/jquery.location_list.js?version=599e2555d
h2
663.65699982271
735.28599995188
3044
12951
200
application/javascript
Script
https://www.meetflings.com/js/join/modern/formValidation.js?version=599e2555d
h2
664.06399989501
818.7039999757
1762
6859
200
application/javascript
Script
https://www.meetflings.com/js/join/modern/modernFormValidation.js?version=599e2555d
h2
664.4039999228
804.85199997202
4668
26180
200
application/javascript
Script
https://notifybrowser.com/webpush.js
h2
664.70199986361
764.90799989551
2384
3526
200
application/javascript
Script
https://www.meetflings.com/js/push-notifications.js
h2
665.03099980764
872.85899999551
1689
4795
200
application/javascript
Script
https://www.meetflings.com/js/ads.js?adids=1&banner_id=1
h2
665.487999795
735.62199994922
470
118
200
application/javascript
Script
https://www.meetflings.com/js/aiCont.js
h2
665.70599982515
736.38199991547
1013
2079
200
application/javascript
Script
https://www.meetflings.com/libs/templates/default/components_new/push_notifications/img/modal_october_thumb.jpg
h2
886.04699983262
955.98099986091
39058
38719
200
image/jpeg
Image
https://www.meetflings.com/images/whitelabel/64374/landing_pages/logo_57.png
h2
890.14099980704
958.967999788
4835
4553
200
image/png
Image
https://www.meetflings.com/images/whitelabel/64374/landing_pages/305/img/2/body.jpg
h2
944.0539998468
1083.9629999828
445500
445214
200
image/jpeg
Image
https://fonts.gstatic.com/s/opensans/v28/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
h2
948.17999983206
951.23299979605
40484
39556
200
font/woff2
Font
https://use.fontawesome.com/releases/v5.4.1/webfonts/fa-solid-900.woff2
h2
950.42299991474
984.15199993178
73134
72000
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v29/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
951.58699993044
955.24799986742
11960
11032
200
font/woff2
Font
https://use.fontawesome.com/releases/v5.4.1/webfonts/fa-regular-400.woff2
h2
952.4299998302
1078.9089999162
15992
14880
200
font/woff2
Font
https://www.meetflings.com/includes/ajax_location_list.php
h2
1025.1660000067
1145.8819999825
487
74
200
text/html
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)
688.716
7.884
697.4
7.815
928.483
46.385
974.892
42.578
1028.588
16.895
1046.827
17.463
1071.062
5.269
1076.679
5.377
1184.864
7.956
1192.86
26.467
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

Time to Interactive — 4.8 s
The time taken for the page to become fully interactive.
Speed Index — 4.6 s
The time taken for the page contents to be visibly populated.

Audits

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

Other

Properly size images — Potential savings of 14 KiB
Images can slow down the page's load time. Meetflings.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.meetflings.com/libs/templates/default/components_new/push_notifications/img/modal_october_thumb.jpg
38719
14707
Minify JavaScript — Potential savings of 5 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Meetflings.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.meetflings.com/js/join/jquery.formValidation.js
4579
3035
https://www.meetflings.com/js/join/modern/modernFormValidation.js?version=599e2555d
4668
2246

Metrics

First Contentful Paint — 4.6 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 7.3 s
The timing of the largest text or image that is painted.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 2,500 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Meetflings.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Catamaran&display=swap
1214
780
https://use.fontawesome.com/releases/v5.4.1/css/all.css
11904
930
https://fonts.googleapis.com/css2?family=Open+Sans:wght@400;600;700;800&family=Roboto:wght@400;700&display=swap
1785
150
https://www.meetflings.com/js/jquery.min.js
36095
900
https://www.meetflings.com/js/jquery-ui.min.js
80696
1200
https://www.meetflings.com/js/jquery.usernameverifyservice.js
828
150
https://www.meetflings.com/js/join/modern/formValidation.js?version=599e2555d
1762
150
https://notifybrowser.com/webpush.js
2384
780
Reduce unused JavaScript — Potential savings of 68 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.meetflings.com/js/jquery-ui.min.js
80696
69763
Serve images in next-gen formats — Potential savings of 184 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.meetflings.com/images/whitelabel/64374/landing_pages/305/img/2/body.jpg
445214
169733.35
https://www.meetflings.com/libs/templates/default/components_new/push_notifications/img/modal_october_thumb.jpg
38719
18453.7
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Meetflings.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://meetflings.com/
630
https://meetflings.com/
480
https://www.meetflings.com/index.php
0
Serve static assets with an efficient cache policy — 17 resources found
Meetflings.com 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://www.meetflings.com/images/whitelabel/64374/landing_pages/305/img/2/body.jpg
172800000
445500
https://www.meetflings.com/js/jquery-ui.min.js
172800000
80696
https://www.meetflings.com/libs/templates/default/components_new/push_notifications/img/modal_october_thumb.jpg
172800000
39058
https://www.meetflings.com/js/jquery.min.js
172800000
36095
https://www.meetflings.com/css/jquery/jquery-ui.css
172800000
10055
https://www.meetflings.com/images/whitelabel/64374/landing_pages/logo_57.png
172800000
4835
https://www.meetflings.com/js/join/modern/modernFormValidation.js?version=599e2555d
172800000
4668
https://www.meetflings.com/js/join/jquery.formValidation.js
172800000
4579
https://www.meetflings.com/js/jquery.location_list.js?version=599e2555d
172800000
3044
https://notifybrowser.com/webpush.js
172800000
2384
https://www.meetflings.com/js/join/modern/formValidation.js?version=599e2555d
172800000
1762
https://www.meetflings.com/js/push-notifications.js
172800000
1689
https://www.meetflings.com/js/landing_pages/footerLinks.js?version=599e2555d
172800000
1203
https://www.meetflings.com/js/aiCont.js
172800000
1013
https://www.meetflings.com/js/jquery.emailverifyservice.js
172800000
979
https://www.meetflings.com/js/jquery.usernameverifyservice.js
172800000
828
https://www.meetflings.com/js/ads.js?adids=1&banner_id=1
172800000
470
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://use.fontawesome.com/releases/v5.4.1/webfonts/fa-solid-900.woff2
33.729000017047
https://use.fontawesome.com/releases/v5.4.1/webfonts/fa-regular-400.woff2
126.47900008596
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.meetflings.com/libs/templates/default/components_new/push_notifications/img/modal_october_thumb.jpg
https://www.meetflings.com/images/whitelabel/64374/landing_pages/logo_57.png
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of meetflings.com on mobile screens.
First Contentful Paint (3G) — 9876 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
78

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of meetflings.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.
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.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[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"]`
Meetflings.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Navigation

Heading elements are not 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.
Failing Elements

Internationalization and localization

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
67

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.4.0
jQuery UI
1.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.
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://meetflings.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
2
Medium
3
High

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.meetflings.com/images/whitelabel/64374/landing_pages/logo_57.png
231 x 57
231 x 57
462 x 114

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
62

SEO

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

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

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of meetflings.com on mobile screens.
Document doesn't use 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 not 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

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

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

PWA

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

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

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
Does not set 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 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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of meetflings.com on mobile screens.
Does not provide 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.
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: 35.203.113.247
Continent: North America
Country: United States
United States Flag
Region: California
City: Mountain View
Longitude: -122.0775
Latitude: 37.4056
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Google LLC
Registration

Domain Registrant

Private Registration: Yes
Name: Redacted for Privacy
Organization: Privacy service provided by Withheld for Privacy ehf
Country: IS
City: Reykjavik
State: Capital Region
Post Code: 101
Email: 3b81153541ae4277a8d2e610cc02b932.protect@withheldforprivacy.com
Phone: +354.4212434
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NameCheap, Inc. 104.16.99.56
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: meetflings.com
Issued By: R3
Valid From: 12th January, 2023
Valid To: 12th April, 2023
Subject: CN = meetflings.com
Hash: cc43bd25
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x030C408FA39C11B484C3F9756C2848A16BF8
Serial Number (Hex): 030C408FA39C11B484C3F9756C2848A16BF8
Valid From: 12th January, 2024
Valid To: 12th April, 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 : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : Jan 12 11:07:22.467 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:23:49:A1:59:97:CA:61:04:D4:48:07:08:
F9:BC:D8:9A:27:92:A1:91:4C:22:B2:76:AE:CC:AD:6A:
41:4E:5A:1E:02:20:09:38:19:F8:20:ED:43:9A:7E:B0:
B8:14:D6:71:80:D1:37:C4:65:41:A6:13:37:C6:F4:26:
68:5A:FC:7D:34:ED
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Jan 12 11:07:22.487 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:34:F0:B4:81:B8:12:D2:F6:4F:48:AB:A5:
5C:43:74:B6:08:36:DC:9E:DF:FA:DE:AD:AE:0B:4D:09:
75:5E:42:21:02:21:00:DC:31:D3:31:E3:08:A1:C2:1D:
1B:5C:99:A5:8D:24:B4:03:C0:99:8E:C6:F1:DB:FF:97:
FA:34:0A:21:9E:F6:C2
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:mobile.meetflings.com
DNS:www.meetflings.com
DNS:meetflings.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
meetflings.com. 35.203.113.247 IN 24

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 21st February, 2023
Content-Type: text/html; charset=UTF-8
Expires: 19th November, 1981
Cache-Control: private, must-revalidate
expires: 31st December, 1969
Set-Cookie: *
Pragma: no-cache
pragma: no-cache
X-Asset-Type: dynamic
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff

Whois Lookup

Created: 19th November, 2021
Changed: 27th October, 2022
Expires: 19th November, 2023
Registrar: NAMECHEAP INC
Status: clientTransferProhibited
Nameservers: ns1.easy53.com
ns2.simple53.com
Owner Name: Redacted for Privacy
Owner Organization: Privacy service provided by Withheld for Privacy ehf
Owner Street: Kalkofnsvegur 2
Owner Post Code: 101
Owner City: Reykjavik
Owner State: Capital Region
Owner Country: IS
Owner Phone: +354.4212434
Owner Email: 3b81153541ae4277a8d2e610cc02b932.protect@withheldforprivacy.com
Admin Name: Redacted for Privacy
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2
Admin Post Code: 101
Admin City: Reykjavik
Admin State: Capital Region
Admin Country: IS
Admin Phone: +354.4212434
Admin Email: 3b81153541ae4277a8d2e610cc02b932.protect@withheldforprivacy.com
Tech Name: Redacted for Privacy
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2
Tech Post Code: 101
Tech City: Reykjavik
Tech State: Capital Region
Tech Country: IS
Tech Phone: +354.4212434
Tech Email: 3b81153541ae4277a8d2e610cc02b932.protect@withheldforprivacy.com
Full Whois: Domain name: meetflings.com
Registry Domain ID: 2656259336_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2022-10-27T16:41:04.01Z
Creation Date: 2021-11-19T23:42:50.00Z
Registrar Registration Expiration Date: 2023-11-19T23:42:50.00Z
Registrar: NAMECHEAP INC
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.9854014545
Reseller: NAMECHEAP INC
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Redacted for Privacy
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: Kalkofnsvegur 2
Registrant City: Reykjavik
Registrant State/Province: Capital Region
Registrant Postal Code: 101
Registrant Country: IS
Registrant Phone: +354.4212434
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: 3b81153541ae4277a8d2e610cc02b932.protect@withheldforprivacy.com
Registry Admin ID:
Admin Name: Redacted for Privacy
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2
Admin City: Reykjavik
Admin State/Province: Capital Region
Admin Postal Code: 101
Admin Country: IS
Admin Phone: +354.4212434
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: 3b81153541ae4277a8d2e610cc02b932.protect@withheldforprivacy.com
Registry Tech ID:
Tech Name: Redacted for Privacy
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2
Tech City: Reykjavik
Tech State/Province: Capital Region
Tech Postal Code: 101
Tech Country: IS
Tech Phone: +354.4212434
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: 3b81153541ae4277a8d2e610cc02b932.protect@withheldforprivacy.com
Name Server: ns1.easy53.com
Name Server: ns2.simple53.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-02-21T06:30:17.62Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

Nameservers

Name IP Address
ns1.easy53.com 35.203.38.102
ns2.simple53.com 35.203.38.102
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address