grindr.com

grindr.com is SSL secured

Free website and domain report on grindr.com

Last Updated: 9th October, 2023 Update Now
Overview

Snoop Summary for grindr.com

This is a free and comprehensive report about grindr.com. Grindr.com is hosted in United States on a server with an IP address of 18.211.206.63, where USD is the local currency and the local language is English. Our records indicate that grindr.com is privately registered by Domains By Proxy, LLC. Grindr.com is expected to earn an estimated $19 USD per day from advertising revenue. The sale of grindr.com would possibly be worth $14,157 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Grindr.com is very popular with an estimated 6,800 daily unique visitors. This report was last updated 9th October, 2023.

About grindr.com

Site Preview:
Title: Grindr: The World’s Largest Social Networking App for LGBTQ People.
Description: Grindr is the world’s largest social networking app for gay, bi, trans, and queer people. Download Grindr today to discover, connect to, and explore the queer world around you.
Keywords and Tags: adult content, dating, mobile phone, personals, popular
Related Terms: grindr, grindr for pc, largest waterfall in the world, lgbtq, networking, queer, queer bars, queer history, worldmoneytrade networking
Fav Icon:
Age: Over 17 years old
Domain Created: 13th June, 2006
Domain Updated: 14th June, 2022
Domain Expires: 13th June, 2023
Review

Snoop Score

3/5 (Great!)

Valuation

$14,157 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 65,253
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: 6,800
Monthly Visitors: 206,971
Yearly Visitors: 2,482,000
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $19 USD
Monthly Revenue: $590 USD
Yearly Revenue: $7,074 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: grindr.com 10
Domain Name: grindr 6
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.83 seconds
Load Time Comparison: Faster than 85% of sites

PageSpeed Insights

Avg. (All Categories) 79
Performance 95
Accessibility 93
Best Practices 92
SEO 92
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.grindr.com/
Updated: 16th November, 2022

0.68 seconds
First Contentful Paint (FCP)
93%
3%
4%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

95

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for grindr.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 — 0.7 s
The time taken for the page to become fully interactive.
Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.
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).
Cumulative Layout Shift — 0.003
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
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://grindr.com/
http/1.1
0
113.71199972928
258
0
302
text/html
https://www.grindr.com/
h2
114.18899986893
230.6099999696
5665
20169
200
text/html
Document
https://www.grindr.com/assets/fonts/DINOT.otf
h2
242.51900007948
348.77600008622
32732
43784
200
text/plain
Font
https://www.grindr.com/assets/fonts/DINOT-Bold.otf
h2
242.69999982789
278.95399974659
32577
45608
200
text/plain
Font
https://www.grindr.com/assets/fonts/DINOT-Medium.otf
h2
242.96199996024
358.8649998419
32295
44944
200
text/plain
Font
https://www.grindr.com/assets/css/main.css
h2
243.33800002933
320.342999883
8942
41544
200
text/css
Stylesheet
https://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/OtAutoBlock.js
h2
244.09099994227
268.53699982166
3161
6115
200
application/x-javascript
Script
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js
h2
244.5000000298
269.12199985236
8030
21748
200
application/javascript
Script
https://www.grindr.com/assets/js/OptanonWrapper.js
h2
244.75999968126
343.20400003344
2330
29
200
application/javascript
Script
https://www.grindr.com/assets/images/logo-small-black.png
h2
348.02099969238
435.01099990681
5392
2978
200
image/webp
Image
https://www.grindr.com/assets/images/arrow.png
h2
348.52699982002
413.93999988213
2550
185
200
image/png
Image
https://www.grindr.com/assets/images/fb-logo.png
h2
351.400999818
428.20600001141
2800
396
200
image/webp
Image
https://www.grindr.com/assets/images/tw-logo.png
h2
351.87199991196
441.82300008833
3285
882
200
image/webp
Image
https://www.grindr.com/assets/images/ig-logo.png
h2
351.97399975732
461.61999972537
3530
1126
200
image/webp
Image
https://www.grindr.com/assets/images/yt-logo.png
h2
352.07200003788
435.68899994716
2717
314
200
image/webp
Image
https://www.grindr.com/assets/images/tt-logo.svg
h2
352.19000000507
402.93100010604
2833
988
200
image/svg+xml
Image
https://www.grindr.com/assets/images/lk-logo.svg
h2
352.30499971658
422.16699989513
2628
524
200
image/svg+xml
Image
https://www.grindr.com/assets/images/download-inactive.png
h2
352.39599971101
400.70599969476
3426
1012
200
image/webp
Image
https://www.grindr.com/assets/images/download-active.png
h2
352.49099973589
453.03800003603
3048
636
200
image/webp
Image
https://www.grindr.com/assets/images/about-inactive.png
h2
352.58999979123
407.09799993783
2948
538
200
image/webp
Image
https://www.grindr.com/assets/images/about-active.png
h2
352.70199971274
439.65200008824
2775
368
200
image/webp
Image
https://www.grindr.com/assets/images/help.png
h2
352.79699973762
451.91900013015
3131
730
200
image/webp
Image
https://www.grindr.com/assets/images/menu.png
h2
352.90100006387
445.37199987099
2504
106
200
image/webp
Image
https://www.grindr.com/assets/images/phone-logo.svg
h2
353.40699972585
421.20799981058
5539
7716
200
image/svg+xml
Image
https://www.grindr.com/assets/images/close-icon.svg
h2
353.97400008515
403.37800001726
2469
262
200
image/svg+xml
Image
https://www.grindr.com/assets/images/AppStore-Badge.svg
h2
355.43099977076
424.14700007066
6242
10804
200
image/svg+xml
Image
https://play.google.com/intl/en_us/badges/static/images/badges/en_badge_web_generic.png
h2
355.72599992156
377.17100000009
5827
4904
200
image/png
Image
https://www.grindr.com/assets/images/iphone.webp
h2
355.88399972767
458.92299991101
617187
614886
200
image/webp
Image
https://www.grindr.com/assets/js/jquery-3.5.1.min.js
h2
347.03399986029
441.10699975863
33190
89476
200
application/javascript
Script
https://www.grindr.com/assets/js/mini-cookies.js
h2
347.29299973696
411.92899970338
3302
2564
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-3ZJKH4GWHP
h2
356.00899998099
396.38199983165
76648
216538
200
application/javascript
Script
https://www.grindr.com/assets/js/gtag.js
h2
347.46100008488
414.39800010994
2973
1356
200
application/javascript
Script
https://www.grindr.com/assets/js/common.js
h2
347.66899980605
443.02899995819
3787
3684
200
application/javascript
Script
https://www.grindr.com/assets/js/feature-detection.js
h2
347.87900000811
425.98900012672
2926
1244
200
application/javascript
Script
https://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/9e16a97b-843a-45b0-b439-8c199bf3bdd1.json
h2
336.05000004172
368.73300001025
2741
4933
200
application/x-javascript
XHR
https://geolocation.onetrust.com/cookieconsentpub/v1/geo/location
h2
397.77599973604
431.73500010744
465
75
200
application/json
XHR
https://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
h2
491.67199991643
527.1529997699
92303
384522
200
application/javascript
Script
data
549.63300004601
549.74799975753
0
34
200
image/webp
Image
https://www.google-analytics.com/g/collect?v=2&tid=G-3ZJKH4GWHP&gtm=2oeb90&_p=1255674221&gcs=G100&cid=963774103.1668642839&ul=en-us&sr=800x600&uaa=x86&uab=&uafvl=&uamb=0&uam=&uap=macOS&uapv=10.15.7&uaw=0&_s=1&sid=1668642839&sct=1&seg=0&dl=https%3A%2F%2Fwww.grindr.com%2F&dt=Grindr%3A%20The%20World%E2%80%99s%20Largest%20Social%20Networking%20App%20for%20LGBTQ%20People.&en=page_view&_fv=1&_nsi=1&_ss=1&_ee=1&ep.anonymize_ip=true
617.94799985364
660.08799988776
0
0
-1
Ping
https://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/cf189803-9edd-4998-957f-f89f174e6695/en.json
h2
650.57000005618
682.99399968237
14741
57040
200
application/x-javascript
Fetch
https://cdn.cookielaw.org/scripttemplates/202209.1.0/assets/otFlat.json
h2
714.52699974179
742.90199996904
3880
13129
200
application/json
Fetch
https://cdn.cookielaw.org/scripttemplates/202209.1.0/assets/v2/otPcTab.json
h2
715.89499991387
744.41300006583
14927
64700
200
application/json
Fetch
https://cdn.cookielaw.org/scripttemplates/202209.1.0/assets/otCommonStyles.css
h2
716.38099988922
743.90399968252
5173
22226
200
text/css
Fetch
https://www.google-analytics.com/g/collect?v=2&tid=G-3ZJKH4GWHP&gtm=2oeb90&_p=1255674221&gcs=G100&cid=963774103.1668642839&ul=en-us&sr=800x600&uaa=x86&uab=&uafvl=&uamb=0&uam=&uap=macOS&uapv=10.15.7&uaw=0&_s=2&sid=1668642839&sct=1&seg=0&dl=https%3A%2F%2Fwww.grindr.com%2F&dt=Grindr%3A%20The%20World%E2%80%99s%20Largest%20Social%20Networking%20App%20for%20LGBTQ%20People.&en=scroll&ep.anonymize_ip=true&epn.percent_scrolled=90&_et=39
727.36199991778
729.69599999487
0
0
-1
Ping
data
769.1839998588
769.38699977472
0
817
200
image/svg+xml
Image
https://cdn.cookielaw.org/logos/3c925b0e-cf8e-4603-92ba-688f45b32d72/66b90db3-564f-4f65-9aa3-37158aeb3a6b/Grindr_Logo_Grindr_Logo_mix_white.png
h2
830.50199970603
856.59600002691
289753
288911
200
application/octet-stream
Image
https://cdn.cookielaw.org/logos/static/poweredBy_ot_logo.svg
h2
830.67600009963
857.40699991584
2323
2998
200
image/svg+xml
Image
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)
237.355
21.042
327.15
9.892
347.343
7.422
354.78
30.098
398.542
5.029
403.584
5.665
414.657
6.071
430.686
5.633
443.044
23.616
473.214
13.42
491.874
6.74
504.122
5.466
511.681
5.285
520.65
18.987
544.701
6.8
551.907
19.759
573.49
6.582
580.333
40.621
622.032
11.905
634.275
15.444
650.488
8.256
663.562
9.764
673.654
5.402
688.202
29.732
718.33
12.154
748.982
82.467
850.533
10.493
863.051
6.108
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. Grindr.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Grindr.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Grindr.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 17 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Grindr.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)
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} ...
20510
17461
Reduce unused JavaScript — Potential savings of 95 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://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
92303
47720
https://www.googletagmanager.com/gtag/js?id=G-3ZJKH4GWHP
76648
28806
https://www.grindr.com/assets/js/jquery-3.5.1.min.js
33190
20976
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 120 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.grindr.com/
117.417
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Grindr.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://grindr.com/
190
https://www.grindr.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Grindr.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 6 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://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
6564
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,324 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.grindr.com/assets/images/iphone.webp
617187
https://cdn.cookielaw.org/logos/3c925b0e-cf8e-4603-92ba-688f45b32d72/66b90db3-564f-4f65-9aa3-37158aeb3a6b/Grindr_Logo_Grindr_Logo_mix_white.png
289753
https://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
92303
https://www.googletagmanager.com/gtag/js?id=G-3ZJKH4GWHP
76648
https://www.grindr.com/assets/js/jquery-3.5.1.min.js
33190
https://www.grindr.com/assets/fonts/DINOT.otf
32732
https://www.grindr.com/assets/fonts/DINOT-Bold.otf
32577
https://www.grindr.com/assets/fonts/DINOT-Medium.otf
32295
https://cdn.cookielaw.org/scripttemplates/202209.1.0/assets/v2/otPcTab.json
14927
https://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/cf189803-9edd-4998-957f-f89f174e6695/en.json
14741
Avoids an excessive DOM size — 385 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
385
Maximum DOM Depth
16
Maximum Child Elements
13
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Grindr.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.2 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.grindr.com/
213.758
5.252
2.275
Unattributable
179.882
32.294
0
https://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
110.472
78.158
11.112
https://www.googletagmanager.com/gtag/js?id=G-3ZJKH4GWHP
75.647
65.825
4.729
Minimizes main-thread work — 0.6 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
234.503
Other
197.168
Rendering
81.821
Style & Layout
77.255
Parse HTML & CSS
25.989
Script Parsing & Compilation
21.85
Garbage Collection
5.301
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 • 1,324 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
1355953
Image
21
972907
Script
10
228650
Font
3
97604
Other
9
42185
Stylesheet
1
8942
Document
1
5665
Media
0
0
Third-party
15
519972
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)
437497
0
76648
0
5827
0
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
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 — 4 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0026241134751773
0.00059932771867612
4.2027843446283E-5
3.7202302775589E-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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
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 grindr.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

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

Other

Eliminate render-blocking resources — Potential savings of 260 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Grindr.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://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/OtAutoBlock.js
3161
230
Properly size images — Potential savings of 538 KiB
Images can slow down the page's load time. Grindr.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.grindr.com/assets/images/iphone.webp
614886
551371

Other

Serve static assets with an efficient cache policy — 33 resources found
Grindr.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.grindr.com/assets/js/jquery-3.5.1.min.js
7200000
33190
https://www.grindr.com/assets/css/main.css
7200000
8942
https://www.grindr.com/assets/js/common.js
7200000
3787
https://www.grindr.com/assets/js/mini-cookies.js
7200000
3302
https://www.grindr.com/assets/js/gtag.js
7200000
2973
https://www.grindr.com/assets/js/feature-detection.js
7200000
2926
https://www.grindr.com/assets/js/OptanonWrapper.js
7200000
2330
https://cdn.cookielaw.org/logos/3c925b0e-cf8e-4603-92ba-688f45b32d72/66b90db3-564f-4f65-9aa3-37158aeb3a6b/Grindr_Logo_Grindr_Logo_mix_white.png
86400000
289753
https://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
86400000
92303
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js
86400000
8030
https://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/OtAutoBlock.js
86400000
3161
https://cdn.cookielaw.org/logos/static/poweredBy_ot_logo.svg
86400000
2323
https://www.grindr.com/assets/images/iphone.webp
2592000000
617187
https://www.grindr.com/assets/fonts/DINOT.otf
2592000000
32732
https://www.grindr.com/assets/fonts/DINOT-Bold.otf
2592000000
32577
https://www.grindr.com/assets/fonts/DINOT-Medium.otf
2592000000
32295
https://www.grindr.com/assets/images/AppStore-Badge.svg
2592000000
6242
https://www.grindr.com/assets/images/phone-logo.svg
2592000000
5539
https://www.grindr.com/assets/images/logo-small-black.png
2592000000
5392
https://www.grindr.com/assets/images/ig-logo.png
2592000000
3530
https://www.grindr.com/assets/images/download-inactive.png
2592000000
3426
https://www.grindr.com/assets/images/tw-logo.png
2592000000
3285
https://www.grindr.com/assets/images/help.png
2592000000
3131
https://www.grindr.com/assets/images/download-active.png
2592000000
3048
https://www.grindr.com/assets/images/about-inactive.png
2592000000
2948
https://www.grindr.com/assets/images/tt-logo.svg
2592000000
2833
https://www.grindr.com/assets/images/fb-logo.png
2592000000
2800
https://www.grindr.com/assets/images/about-active.png
2592000000
2775
https://www.grindr.com/assets/images/yt-logo.png
2592000000
2717
https://www.grindr.com/assets/images/lk-logo.svg
2592000000
2628
https://www.grindr.com/assets/images/arrow.png
2592000000
2550
https://www.grindr.com/assets/images/menu.png
2592000000
2504
https://www.grindr.com/assets/images/close-icon.svg
2592000000
2469
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.grindr.com/assets/images/tt-logo.svg
https://play.google.com/intl/en_us/badges/static/images/badges/en_badge_web_generic.png
https://www.grindr.com/assets/images/lk-logo.svg
https://www.grindr.com/assets/images/logo-small-black.png
https://www.grindr.com/assets/images/AppStore-Badge.svg
https://www.grindr.com/assets/images/ig-logo.png
https://www.grindr.com/assets/images/tw-logo.png
https://www.grindr.com/assets/images/yt-logo.png
https://www.grindr.com/assets/images/fb-logo.png
https://www.grindr.com/assets/images/arrow.png
https://www.grindr.com/assets/images/arrow.png
https://www.grindr.com/assets/images/arrow.png
https://www.grindr.com/assets/images/arrow.png
https://www.grindr.com/assets/images/arrow.png
https://www.grindr.com/assets/images/arrow.png
93

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of grindr.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 alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

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

Internationalization and localization

`<html>` element has a `[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.

Audio and video

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

Best practices

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that grindr.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.
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
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.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://grindr.com/
Allowed
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for grindr.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 grindr.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.
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.

Crawling and Indexing

Links are not 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.

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

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 grindr.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.
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 grindr.com on 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 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) 68
Performance 49
Accessibility 90
Best Practices 83
SEO 86
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.grindr.com/
Updated: 16th November, 2022

1.50 seconds
First Contentful Paint (FCP)
82%
11%
7%

0.02 seconds
First Input Delay (FID)
93%
5%
2%

49

Performance

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

Metrics

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

Other

Properly size images
Images can slow down the page's load time. Grindr.com should consider serving more appropriate-sized images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Grindr.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Grindr.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 19 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Grindr.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)
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} ...
21894
19258
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 110 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.grindr.com/
108.462
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Grindr.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://grindr.com/
630
https://www.grindr.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Grindr.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 6 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://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
6564
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids an excessive DOM size — 670 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
670
Maximum DOM Depth
15
Maximum Child Elements
14
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Grindr.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 — 1.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)
Unattributable
834.38
367.404
0
https://www.grindr.com/
645.868
21.032
5.172
https://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
500.72
308.748
42.856
https://www.googletagmanager.com/gtag/js?id=G-3ZJKH4GWHP
194.408
178.348
13.164
https://www.grindr.com/assets/js/jquery-3.5.1.min.js
83.112
71.596
7.676
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js
79.916
66.184
6.152
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 — 49 requests • 5,874 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
49
6015459
Image
23
5552314
Script
11
244514
Other
10
106419
Font
3
97604
Stylesheet
1
8943
Document
1
5665
Media
0
0
Third-party
17
600058
Minimize third-party usage — Third-party code blocked the main thread for 200 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)
517595
137.788
76636
59.732
5827
0
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
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.03476806640625
0.00096092224121094
0.00010093688964844
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 — 8 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)
Unattributable
7925
452
https://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
8377
212
https://www.googletagmanager.com/gtag/js?id=G-3ZJKH4GWHP
3357
112
https://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
7854
71
https://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/OtAutoBlock.js
29610
70
https://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/OtAutoBlock.js
3660
63
https://www.grindr.com/
1410
61
https://www.googletagmanager.com/gtag/js?id=G-3ZJKH4GWHP
3301
56
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
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 grindr.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

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://grindr.com/
http/1.1
0
40.47900007572
258
0
302
text/html
https://www.grindr.com/
h2
40.882000001147
148.34900002461
5665
20169
200
text/html
Document
https://www.grindr.com/assets/fonts/DINOT.otf
h2
160.0070000859
200.01900009811
32732
43784
200
text/plain
Font
https://www.grindr.com/assets/fonts/DINOT-Bold.otf
h2
160.24400002789
195.93000004534
32577
45608
200
text/plain
Font
https://www.grindr.com/assets/fonts/DINOT-Medium.otf
h2
160.57300008833
199.15800006129
32295
44944
200
text/plain
Font
https://www.grindr.com/assets/css/main.css
h2
160.7490000315
223.86200004257
8943
41544
200
text/css
Stylesheet
https://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/OtAutoBlock.js
h2
161.13900009077
272.53900002688
3149
6115
200
application/x-javascript
Script
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js
h2
161.44699999131
172.3860000493
8030
21748
200
application/javascript
Script
https://www.grindr.com/assets/js/OptanonWrapper.js
h2
161.75400000066
197.61600007769
2330
29
200
application/javascript
Script
https://www.grindr.com/assets/images/logo-small-black.png
h2
286.01400007028
304.04000007547
5392
2978
200
image/webp
Image
https://www.grindr.com/assets/images/arrow.png
h2
286.89900005702
336.5820000181
2550
185
200
image/png
Image
https://www.grindr.com/assets/images/fb-logo.png
h2
287.1640000958
326.03100000415
2800
396
200
image/webp
Image
https://www.grindr.com/assets/images/tw-logo.png
h2
287.28100005537
308.45600005705
3285
882
200
image/webp
Image
https://www.grindr.com/assets/images/ig-logo.png
h2
287.42700000294
332.62100000866
3532
1126
200
image/webp
Image
https://www.grindr.com/assets/images/yt-logo.png
h2
287.56299999077
317.96300003771
2717
314
200
image/webp
Image
https://www.grindr.com/assets/images/tt-logo.svg
h2
287.66900009941
316.09300000127
2833
988
200
image/svg+xml
Image
https://www.grindr.com/assets/images/lk-logo.svg
h2
287.83100005239
341.20900009293
2628
524
200
image/svg+xml
Image
https://www.grindr.com/assets/images/download-inactive.png
h2
288.22099999525
331.91500010435
3428
1012
200
image/webp
Image
https://www.grindr.com/assets/images/download-active.png
h2
288.42700005043
344.68600002583
3048
636
200
image/webp
Image
https://www.grindr.com/assets/images/about-inactive.png
h2
288.64899999462
315.67400007043
2949
538
200
image/webp
Image
https://www.grindr.com/assets/images/about-active.png
h2
288.7880000053
319.11700009368
2776
368
200
image/webp
Image
https://www.grindr.com/assets/images/help.png
h2
289.29600003175
307.65299999621
3130
730
200
image/webp
Image
https://www.grindr.com/assets/images/menu.png
h2
289.46900006849
311.71900010668
2505
106
200
image/webp
Image
https://www.grindr.com/assets/images/phone-logo.svg
h2
289.6330000367
315.16900006682
5539
7716
200
image/svg+xml
Image
https://www.grindr.com/assets/images/close-icon.svg
h2
289.78300001472
318.72000009753
2469
262
200
image/svg+xml
Image
https://www.grindr.com/assets/images/AppStore-Badge.svg
h2
289.86100002658
352.53000003286
6242
10804
200
image/svg+xml
Image
https://play.google.com/intl/en_us/badges/static/images/badges/en_badge_web_generic.png
h2
289.97600008734
295.90100003406
5827
4904
200
image/png
Image
https://www.grindr.com/assets/images/iphone.webp
h2
290.31200008467
321.55100000091
617187
614886
200
image/webp
Image
https://www.grindr.com/assets/js/jquery-3.5.1.min.js
h2
225.47300008591
286.39700007625
33189
89476
200
application/javascript
Script
https://www.grindr.com/assets/js/mini-cookies.js
h2
274.79100006167
319.61900007445
3302
2564
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-3ZJKH4GWHP
h2
290.41700006928
322.84100004472
76636
216565
200
application/javascript
Script
https://www.grindr.com/assets/js/gtag.js
h2
285.46200005803
311.26099999528
2971
1356
200
application/javascript
Script
https://www.grindr.com/assets/js/common.js
h2
285.652999999
316.55300001148
3788
3684
200
application/javascript
Script
https://www.grindr.com/assets/js/feature-detection.js
h2
285.79200000968
323.70000006631
2925
1244
200
application/javascript
Script
https://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/9e16a97b-843a-45b0-b439-8c199bf3bdd1.json
h2
284.42100004759
308.06599999778
2741
4933
200
application/x-javascript
XHR
https://www.grindr.com/assets/images/mobile-bg.png
h2
312.50900006853
408.94200000912
3475855
3473440
200
image/webp
Image
https://geolocation.onetrust.com/cookieconsentpub/v1/geo/location
h2
339.0800000634
363.66900010034
447
59
200
application/json
XHR
data
370.59800000861
370.70100009441
0
34
200
image/webp
Image
https://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
h2
382.59400008246
413.54400001001
92303
384522
200
application/javascript
Script
https://www.grindr.com/assets/images/mobile-bg.webp
h2
384.30700008757
432.3110000696
1103561
1101258
200
image/webp
Image
https://www.google-analytics.com/g/collect?v=2&tid=G-3ZJKH4GWHP&gtm=2oeb90&_p=1825355725&gcs=G100&cid=651922611.1668642859&ul=en-us&sr=360x640&uaa=&uab=&uafvl=&uamb=1&uam=Moto%20G4&uap=Android&uapv=6.0&uaw=0&_s=1&sid=1668642859&sct=1&seg=0&dl=https%3A%2F%2Fwww.grindr.com%2F&dt=Grindr%3A%20The%20World%E2%80%99s%20Largest%20Social%20Networking%20App%20for%20LGBTQ%20People.&en=page_view&_fv=1&_nsi=1&_ss=1&_ee=1&ep.anonymize_ip=true
434.36400010251
449.28300008178
0
0
-1
Ping
https://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/57a3e52c-5411-47a4-aa23-36c6ce75143f/en.json
h2
482.87300008815
512.82800000627
23368
113917
200
application/x-javascript
Fetch
https://cdn.cookielaw.org/vendorlist/iab2Data.json
h2
483.65200008266
519.7820001049
53658
369825
200
application/x-javascript
Fetch
https://cdn.cookielaw.org/scripttemplates/202209.1.0/otTCF.js
h2
485.0050000241
508.95899999887
15891
69465
200
application/javascript
Script
https://cdn.cookielaw.org/scripttemplates/202209.1.0/assets/otFlat.json
h2
642.46600004844
661.09900001902
3880
13129
200
application/json
Fetch
https://cdn.cookielaw.org/scripttemplates/202209.1.0/assets/v2/otPcPanel.json
h2
643.19299999624
669.96700002346
14254
66200
200
application/json
Fetch
https://cdn.cookielaw.org/scripttemplates/202209.1.0/assets/otCookieSettingsButton.json
h2
644.09900002647
660.73800006416
2640
4706
200
application/json
Fetch
https://cdn.cookielaw.org/scripttemplates/202209.1.0/assets/otCommonStyles.css
h2
644.95300000999
660.25000007357
5173
22226
200
text/css
Fetch
https://cdn.cookielaw.org/logos/3c925b0e-cf8e-4603-92ba-688f45b32d72/cb48936d-0084-4ea2-9fc1-cb9195503954/d9ad92e9-380e-464f-9715-cefcccb37759/Grindr_Logo_Grindr_Logo_mix_white.png
h2
778.11300009489
797.69100004341
289738
288911
200
image/png
Image
https://cdn.cookielaw.org/logos/static/poweredBy_ot_logo.svg
h2
778.42800004873
795.9780000383
2323
2998
200
image/svg+xml
Image
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)
153.671
15.213
276.915
15.641
292.572
5.242
302.039
5.142
311.639
7.623
320.573
17.413
372.312
11.371
387.321
5.185
392.833
14.045
409.101
27.877
455.015
6.117
461.203
6.885
468.854
17.639
514.53
8.097
526.761
6.065
533.291
113.118
673.159
106.155
790.799
7.728
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.5 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 5.3 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 380 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).

Audits

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

Other

Reduce unused JavaScript — Potential savings of 92 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://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
92303
44063
https://www.googletagmanager.com/gtag/js?id=G-3ZJKH4GWHP
76636
29432
https://www.grindr.com/assets/js/jquery-3.5.1.min.js
33189
20976
Serve images in next-gen formats — Potential savings of 102 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://cdn.cookielaw.org/logos/3c925b0e-cf8e-4603-92ba-688f45b32d72/cb48936d-0084-4ea2-9fc1-cb9195503954/d9ad92e9-380e-464f-9715-cefcccb37759/Grindr_Logo_Grindr_Logo_mix_white.png
288911
104769.25
Minimize main-thread work — 2.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1075.736
Other
573.872
Style & Layout
260.244
Rendering
216.676
Parse HTML & CSS
115.168
Garbage Collection
96.944
Script Parsing & Compilation
82.66

Metrics

Time to Interactive — 17.5 s
The time taken for the page to become fully interactive.
Largest Contentful Paint — 28.0 s
The timing of the largest text or image that is painted.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 980 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Grindr.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://www.grindr.com/assets/css/main.css
8943
150
https://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/OtAutoBlock.js
3149
780
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js
8030
150
Defer offscreen images — Potential savings of 289 KiB
Time to Interactive can be slowed down by resources on the page. Grindr.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.cookielaw.org/logos/3c925b0e-cf8e-4603-92ba-688f45b32d72/cb48936d-0084-4ea2-9fc1-cb9195503954/d9ad92e9-380e-464f-9715-cefcccb37759/Grindr_Logo_Grindr_Logo_mix_white.png
288911
288911
https://play.google.com/intl/en_us/badges/static/images/badges/en_badge_web_generic.png
4904
4904
https://cdn.cookielaw.org/logos/static/poweredBy_ot_logo.svg
2323
2323
Avoid enormous network payloads — Total size was 5,874 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.grindr.com/assets/images/mobile-bg.png
3475855
https://www.grindr.com/assets/images/mobile-bg.webp
1103561
https://www.grindr.com/assets/images/iphone.webp
617187
https://cdn.cookielaw.org/logos/3c925b0e-cf8e-4603-92ba-688f45b32d72/cb48936d-0084-4ea2-9fc1-cb9195503954/d9ad92e9-380e-464f-9715-cefcccb37759/Grindr_Logo_Grindr_Logo_mix_white.png
289738
https://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
92303
https://www.googletagmanager.com/gtag/js?id=G-3ZJKH4GWHP
76636
https://cdn.cookielaw.org/vendorlist/iab2Data.json
53658
https://www.grindr.com/assets/js/jquery-3.5.1.min.js
33189
https://www.grindr.com/assets/fonts/DINOT.otf
32732
https://www.grindr.com/assets/fonts/DINOT-Bold.otf
32577
Serve static assets with an efficient cache policy — 36 resources found
Grindr.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.grindr.com/assets/js/jquery-3.5.1.min.js
7200000
33189
https://www.grindr.com/assets/css/main.css
7200000
8943
https://www.grindr.com/assets/js/common.js
7200000
3788
https://www.grindr.com/assets/js/mini-cookies.js
7200000
3302
https://www.grindr.com/assets/js/gtag.js
7200000
2971
https://www.grindr.com/assets/js/feature-detection.js
7200000
2925
https://www.grindr.com/assets/js/OptanonWrapper.js
7200000
2330
https://cdn.cookielaw.org/logos/3c925b0e-cf8e-4603-92ba-688f45b32d72/cb48936d-0084-4ea2-9fc1-cb9195503954/d9ad92e9-380e-464f-9715-cefcccb37759/Grindr_Logo_Grindr_Logo_mix_white.png
86400000
289738
https://cdn.cookielaw.org/scripttemplates/202209.1.0/otBannerSdk.js
86400000
92303
https://cdn.cookielaw.org/scripttemplates/202209.1.0/otTCF.js
86400000
15891
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js
86400000
8030
https://cdn.cookielaw.org/consent/9e16a97b-843a-45b0-b439-8c199bf3bdd1/OtAutoBlock.js
86400000
3149
https://cdn.cookielaw.org/logos/static/poweredBy_ot_logo.svg
86400000
2323
https://www.grindr.com/assets/images/mobile-bg.png
2592000000
3475855
https://www.grindr.com/assets/images/mobile-bg.webp
2592000000
1103561
https://www.grindr.com/assets/images/iphone.webp
2592000000
617187
https://www.grindr.com/assets/fonts/DINOT.otf
2592000000
32732
https://www.grindr.com/assets/fonts/DINOT-Bold.otf
2592000000
32577
https://www.grindr.com/assets/fonts/DINOT-Medium.otf
2592000000
32295
https://www.grindr.com/assets/images/AppStore-Badge.svg
2592000000
6242
https://www.grindr.com/assets/images/phone-logo.svg
2592000000
5539
https://www.grindr.com/assets/images/logo-small-black.png
2592000000
5392
https://www.grindr.com/assets/images/ig-logo.png
2592000000
3532
https://www.grindr.com/assets/images/download-inactive.png
2592000000
3428
https://www.grindr.com/assets/images/tw-logo.png
2592000000
3285
https://www.grindr.com/assets/images/help.png
2592000000
3130
https://www.grindr.com/assets/images/download-active.png
2592000000
3048
https://www.grindr.com/assets/images/about-inactive.png
2592000000
2949
https://www.grindr.com/assets/images/tt-logo.svg
2592000000
2833
https://www.grindr.com/assets/images/fb-logo.png
2592000000
2800
https://www.grindr.com/assets/images/about-active.png
2592000000
2776
https://www.grindr.com/assets/images/yt-logo.png
2592000000
2717
https://www.grindr.com/assets/images/lk-logo.svg
2592000000
2628
https://www.grindr.com/assets/images/arrow.png
2592000000
2550
https://www.grindr.com/assets/images/menu.png
2592000000
2505
https://www.grindr.com/assets/images/close-icon.svg
2592000000
2469
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.grindr.com/assets/images/tt-logo.svg
https://www.grindr.com/assets/images/lk-logo.svg
https://www.grindr.com/assets/images/logo-small-black.png
https://www.grindr.com/assets/images/phone-logo.svg
https://www.grindr.com/assets/images/ig-logo.png
https://www.grindr.com/assets/images/tw-logo.png
https://www.grindr.com/assets/images/yt-logo.png
https://www.grindr.com/assets/images/fb-logo.png
https://www.grindr.com/assets/images/help.png
https://www.grindr.com/assets/images/about-inactive.png
https://www.grindr.com/assets/images/download-active.png
https://www.grindr.com/assets/images/menu.png
https://www.grindr.com/assets/images/arrow.png
https://www.grindr.com/assets/images/arrow.png
https://www.grindr.com/assets/images/arrow.png
https://www.grindr.com/assets/images/arrow.png
https://www.grindr.com/assets/images/arrow.png
https://www.grindr.com/assets/images/arrow.png
First Contentful Paint (3G) — 4714 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
90

Accessibility

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Grindr.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

Best practices

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that grindr.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.
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
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
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

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.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://grindr.com/
Allowed

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.grindr.com/assets/images/menu.png
24 x 18
46 x 34
48 x 36
86

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for grindr.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 grindr.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
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
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.
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.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not 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.

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

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 grindr.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.
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 grindr.com on 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 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: 18.211.206.63
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 Technologies Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: Registration Private
Organization: Domains By Proxy, LLC
Country: US
City: Tempe
State: Arizona
Post Code: 85284
Email:
Phone: +1.4806242599
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.13.154.6
Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 86/100
WOT Child Safety: 27/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 3rd June, 2022
Valid To: 2nd June, 2023
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 11426941971444667785441899460310656246
Serial Number (Hex): 0898BFBC999B808140FB9E2F8EC4E4F6
Valid From: 3rd June, 2024
Valid To: 2nd June, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Jun 3 10:41:40.654 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:29:E0:9C:98:C7:10:44:DB:88:BB:50:94:
D7:AF:8D:DC:18:45:9E:64:57:6A:B1:C8:45:B2:F5:2A:
14:A7:1B:05:02:20:6C:A9:DA:98:E4:16:4C:D6:62:24:
72:54:12:19:46:D0:A7:76:B7:2E:A8:E7:CF:25:2C:C1:
08:13:C4:82:2A:AB
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : Jun 3 10:41:40.667 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:3F:F9:DD:57:EB:AA:1C:81:65:78:EF:3B:
BE:40:1D:32:EF:9B:4F:83:11:4E:07:A5:F2:4D:BA:21:
85:C2:25:EC:02:20:63:62:F6:3A:67:D3:51:8B:F7:F2:
82:4D:C6:01:7C:7D:BA:79:FE:75:41:BF:D7:CF:1A:A0:
11:D1:91:8E:8D:B2
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 : Jun 3 10:41:40.666 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:A9:1A:B2:A1:29:87:CC:D9:02:E0:44:
67:4B:D8:BA:6C:99:79:98:64:D6:2E:CE:E8:D9:02:D5:
99:7F:52:AB:84:02:21:00:C9:26:44:AD:6F:7B:32:A8:
26:36:64:36:8D:B1:4F:14:72:1F:D6:43:80:89:34:36:
E1:B8:4D:56:A9:42:78:81
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.grindr.com
DNS:sni.cloudflaressl.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
grindr.com. 54.82.71.180 IN 60
grindr.com. 18.211.206.63 IN 60
grindr.com. 23.21.199.168 IN 60

NS Records

Host Nameserver Class TTL
grindr.com. ns-1245.awsdns-27.org. IN 21600
grindr.com. ns-1871.awsdns-41.co.uk. IN 21600
grindr.com. ns-418.awsdns-52.com. IN 21600
grindr.com. ns-623.awsdns-13.net. IN 21600

MX Records

Priority Host Server Class TTL
10 grindr.com. aspmx.l.google.com. IN 1800
20 grindr.com. alt1.aspmx.l.google.com. IN 1800
30 grindr.com. alt2.aspmx.l.google.com. IN 1800
40 grindr.com. aspmx2.googlemail.com. IN 1800
50 grindr.com. aspmx3.googlemail.com. IN 1800

SOA Records

Domain Name Primary NS Responsible Email TTL
grindr.com. ns-1871.awsdns-41.co.uk. awsdns-hostmaster.amazon.com. 900

TXT Records

Host Value Class TTL
grindr.com. MS=ms29911291 IN 60
grindr.com. ZOOM_verify_CvkacunjQA2eucdxNIaU9g IN 60
grindr.com. apple-domain-verification=DCIgLhzlxWqLmK1y IN 60
grindr.com. atlassian-domain-verification=khgDRBAjfdWVLV8MWUyjlfae5T6sj8Oo/5KeiEFS0GJS3fGKItkPn9R44WWM1SsO IN 60
grindr.com. google-site-verification=6FvQSgnraB1gNAF8o7yKxMa5eKybBSPIyypNdiC2CJs IN 60
grindr.com. google-site-verification=NqLyrf9TDfEGu8EhLtjWXS7Z1QIhrfR00uJbKh6bWV0 IN 60
grindr.com. google-site-verification=gzLLvSn3M4vrJOea85nJ84jj0o3ImmMSlmc4xfxwG8M IN 60
grindr.com. google-site-verification=up5kA6X3NEHHmUtDslxWngckoA6tNvvGF5mSrENN3Zw IN 60
grindr.com. h1-domain-verification=ZnF5Vuid7RerpaVeWcSwtqs95Xj8DPZLH9FXuWHNwjtUPjnE IN 60
grindr.com. hcp-domain-verification=d52f90a881ede148382b052fefb206836e626504a53ced49238050df690db826 IN 60
grindr.com. k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCoRFU7ybiBaMoL+6n/n1vzvh8EcsM38OtpGHfCl3+JFLcHNe/GPngYj2oxsV69SkjVW3/+Dj7HiETzJqcUq/GjZz2xWBLYPIQL8VpeWcr3faawsiezk+HhJwAN7NEFcddsergC+tOakmSACmj9G1hYsEyXx1e6tpjuAcedLZgpFQIDAQAB IN 60
grindr.com. onetrust-domain-verification=2d486d28b3734851ba76393c726f501c IN 60
grindr.com. stripe-verification=fb7710997b9764b794779216fd3204168dd98b5e65e689e4ff8bb8b7cb64c38b IN 60
grindr.com. v=spf1 IN 60
grindr.com. workplace-domain-verification=S6EiDBpiwy7WUPmUFu1WC3f6S4zjBI IN 60

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 16th November, 2022
Content-Type: text/html
Cache-Control: public
Expires: 17th November, 2022
Server: cloudflare
Connection: keep-alive
Accept-Ranges: bytes
Cf-Railgun: direct (starting new WAN connection)
Content-Security-Policy: default-src 'self'; script-src 'self' https://cdnjs.cloudflare.com https://cdn.jsdelivr.net/npm/marked@1.2.2/lib/marked.min.js https://extend.vimeocdn.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com https://ssl.google-analytics.com https://www.googletagmanager.com https://cdn.cookielaw.org https://geolocation.onetrust.com https://player.vimeo.com https://hackerone.com; style-src 'self' 'unsafe-inline' https://geolocation.onetrust.com; child-src 'none'; object-src 'self'; frame-ancestors 'self' https://hackerone.com; frame-src 'self' https://hackerone.com https://player.vimeo.com https://www.google.com http://www.youtube.com/; img-src 'self' https://cdn.cookielaw.org data
Last-Modified: 11th November, 2022
Permissions-Policy: accelerometer=(), ambient-light-sensor=(), autoplay=(self), battery=(), camera=(), cross-origin-isolated=(), display-capture=(), document-domain=(), encrypted-media=(), execution-while-not-rendered=(), execution-while-out-of-viewport=(), fullscreen=(), geolocation=(), gyroscope=(), keyboard-map=(), magnetometer=(), microphone=(), midi=(), navigation-override=(), payment=(), picture-in-picture=(), publickey-credentials-get=(), screen-wake-lock=(), sync-xhr=(), usb=(), web-share=(), xr-spatial-tracking=(), clipboard-read=(), clipboard-write=(), gamepad=(), speaker-selection=()
Referrer-Policy: same-origin
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
CF-Cache-Status: DYNAMIC
Set-Cookie: *
CF-RAY: 76b42616cab317f5-EWR

Whois Lookup

Created: 13th June, 2006
Changed: 14th June, 2022
Expires: 13th June, 2023
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns-1245.awsdns-27.org
ns-1871.awsdns-41.co.uk
ns-418.awsdns-52.com
ns-623.awsdns-13.net
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
2155 E Warner Rd
Owner Post Code: 85284
Owner City: Tempe
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=GRINDR.COM
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
2155 E Warner Rd
Admin Post Code: 85284
Admin City: Tempe
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=GRINDR.COM
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
2155 E Warner Rd
Tech Post Code: 85284
Tech City: Tempe
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=GRINDR.COM
Full Whois: Domain Name: GRINDR.COM
Registry Domain ID: 485209817_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2022-06-14T08:46:50Z
Creation Date: 2006-06-13T20:47:32Z
Registrar Registration Expiration Date: 2023-06-13T20:47:32Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 2155 E Warner Rd
Registrant City: Tempe
Registrant State/Province: Arizona
Registrant Postal Code: 85284
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=GRINDR.COM
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 2155 E Warner Rd
Admin City: Tempe
Admin State/Province: Arizona
Admin Postal Code: 85284
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=GRINDR.COM
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 2155 E Warner Rd
Tech City: Tempe
Tech State/Province: Arizona
Tech Postal Code: 85284
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=GRINDR.COM
Name Server: NS-418.AWSDNS-52.COM
Name Server: NS-1245.AWSDNS-27.ORG
Name Server: NS-623.AWSDNS-13.NET
Name Server: NS-1871.AWSDNS-41.CO.UK
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-11-16T23:53:55Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

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

Nameservers

Name IP Address
ns-1245.awsdns-27.org 205.251.196.221
ns-1871.awsdns-41.co.uk 205.251.199.79
ns-418.awsdns-52.com 205.251.193.162
ns-623.awsdns-13.net 205.251.194.111
Related

Subdomains

Domain Subdomain
account

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5

Sites hosted on the same IP address