2girls1cup.ca

2girls1cup.ca is SSL secured

Free website and domain report on 2girls1cup.ca

Last Updated: 3rd January, 2023 Update Now
Overview

Snoop Summary for 2girls1cup.ca

This is a free and comprehensive report about 2girls1cup.ca. The domain 2girls1cup.ca is currently hosted on a server located in United States with the IP address 172.67.152.55, where the local currency is USD and English is the local language. 2girls1cup.ca has the potential to be earning an estimated $6 USD per day from advertising revenue. If 2girls1cup.ca was to be sold it would possibly be worth $4,379 USD (based on the daily revenue potential of the website over a 24 month period). 2girls1cup.ca receives an estimated 2,100 unique visitors every day - a large amount of traffic! This report was last updated 3rd January, 2023.

About 2girls1cup.ca

Site Preview:
Title: WATCH 2 Girls 1 Cup | Uncensored Original Video
Description: The original two girls one cup (2 girls 1 cup/ 2g1c, cup video) love story, captured on film. Watch the artistic masterpiece that will awaken the soul, here.
Keywords and Tags: adult content, extreme, popular, pornography
Related Terms: african cup of nations, asia cup live, betfred cup odds, confederations cup stream, cup board pro, cup e magazine, half of 1 3 cup, interwetten cup live stream, live t20 asia cup, world cup of cricket
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

2/5

Valuation

$4,379 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 275,188
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: 2,100
Monthly Visitors: 63,917
Yearly Visitors: 766,500
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $6 USD
Monthly Revenue: $182 USD
Yearly Revenue: $2,185 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: 2girls1cup.ca 13
Domain Name: 2girls1cup 10
Extension (TLD): ca 2

Page Speed Analysis

Average Load Time: 2.07 seconds
Load Time Comparison: Faster than 44% of sites

PageSpeed Insights

Avg. (All Categories) 78
Performance 99
Accessibility 89
Best Practices 67
SEO 100
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://2girls1cup.ca/
Updated: 3rd January, 2023

1.29 seconds
First Contentful Paint (FCP)
88%
8%
4%

0.00 seconds
First Input Delay (FID)
94%
3%
3%

99

Performance

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

Metrics

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

Audits

First Meaningful Paint — 0.6 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://2girls1cup.ca/
http/1.1
0
27.588999946602
709
0
301
text/plain
https://2girls1cup.ca/
h2
27.960999985225
54.83399995137
6939
19428
200
text/html
Document
https://2girls1cup.ca/wp-includes/css/dist/block-library/style.min.css
h2
61.499999952503
93.098999932408
5038
25245
200
text/css
Stylesheet
https://2girls1cup.ca/wp-includes/css/dist/block-library/theme.min.css
h2
61.736000003293
93.399999896064
1138
1031
200
text/css
Stylesheet
https://fonts.googleapis.com/css
61.565999989398
73.397999978624
0
0
-1
Stylesheet
https://2girls1cup.ca/wp-content/themes/twentysixteen/genericons/genericons.css
h2
62.200999935158
82.197999930941
16605
26703
200
text/css
Stylesheet
https://2girls1cup.ca/wp-content/themes/twentysixteen/style.css
h2
62.437999993563
90.743999928236
11723
56498
200
text/css
Stylesheet
https://2girls1cup.ca/wp-content/themes/twentysixteen/css/blocks.css
h2
62.700999900699
89.944000006653
2198
6258
200
text/css
Stylesheet
https://2girls1cup.ca/wp-includes/js/jquery/jquery.js
h2
62.959000002593
85.991999949329
35593
96866
200
application/javascript
Script
https://2girls1cup.ca/wp-includes/js/jquery/jquery-migrate.min.js
h2
63.189999898896
94.742999994196
4817
10056
200
application/javascript
Script
https://2girls1cup.ca/wp-content/uploads/2015/03/2-girls-1-cup-logo.jpg
h2
121.30599992815
204.1259999387
19880
19137
200
image/jpeg
Image
https://2girls1cup.ca/wp-content/uploads/2018/05/2-girls-1-cup-meme.jpg
h2
121.44899996929
135.63999999315
48389
47638
200
image/jpeg
Image
https://2girls1cup.ca/wp-content/uploads/2022/11/harlem-shake-poop.jpg
h2
121.70499993954
136.70599996112
53055
52314
200
image/jpeg
Image
https://2girls1cup.ca/wp-includes/js/mediaelement/mediaelementplayer-legacy.min.css
h2
96.650999970734
164.4409999717
3282
11232
200
text/css
Stylesheet
https://2girls1cup.ca/wp-includes/js/mediaelement/wp-mediaelement.min.css
h2
115.48899998888
165.59799993411
1810
4163
200
text/css
Stylesheet
https://2girls1cup.ca/wp-content/themes/twentysixteen/js/skip-link-focus-fix.js
h2
119.9229999911
139.3729998963
1067
605
200
application/javascript
Script
https://2girls1cup.ca/wp-content/themes/twentysixteen/js/functions.js
h2
120.09899993427
161.61799989641
2176
4951
200
application/javascript
Script
https://2girls1cup.ca/wp-includes/js/wp-embed.min.js
h2
120.300999959
136.13199989777
1424
1391
200
application/javascript
Script
https://2girls1cup.ca/wp-includes/js/mediaelement/mediaelement-and-player.min.js
h2
120.51299994346
180.54099997971
38548
156559
200
application/javascript
Script
https://2girls1cup.ca/wp-includes/js/mediaelement/mediaelement-migrate.min.js
h2
120.74899999425
135.19599998835
1254
1193
200
application/javascript
Script
https://2girls1cup.ca/wp-includes/js/mediaelement/wp-mediaelement.min.js
h2
120.97099993844
135.92899998184
1187
907
200
application/javascript
Script
https://2girls1cup.ca/wp-includes/js/mediaelement/renderers/vimeo.min.js
h2
121.15799996536
152.24899991881
2915
6170
200
application/javascript
Script
https://suborecho.com/cqDY9z6.bl2/5-lkSbWBQr9ANGDTUey/NDDygm5GNuC/0g0/NUTIIn0OOoDwkg1K
h2
121.94300000556
295.58899998665
423
0
404
text/plain
Script
data
130.3959999932
130.53899991792
0
715
200
image/png
Image
data
132.96199997421
133.05199996103
0
380
200
image/svg+xml
Image
https://2girls1cup.ca/wp-content/uploads/2015/03/2girls1cupvideo.mp4?_=1
h2
154.28199991584
289.17999996338
10368505
1048576
206
video/mp4
Media
data
159.85499997623
159.98299990315
0
547
200
image/svg+xml
Image
data
161.65699996054
161.76299995277
0
552
200
image/svg+xml
Image
data
164.07299996354
164.19199993834
0
177
200
image/svg+xml
Image
data
166.41599999275
166.55500000343
0
351
200
image/svg+xml
Image
data
168.05300000124
168.14399999566
0
242
200
image/svg+xml
Image
https://2girls1cup.ca/wp-includes/js/mediaelement/mejs-controls.svg
h2
269.59399995394
299.67999993823
2072
4598
200
image/svg+xml
Image
https://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1672704000
h2
281.05399990454
297.41100000683
16019
39266
200
application/javascript
Script
https://2girls1cup.ca/wp-content/uploads/2015/03/2girls1cupvideo.mp4?_=1
h2
292.79400000814
404.34299991466
10368513
1048576
206
video/mp4
Media
https://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/pica.js
h2
316.12599990331
350.09699990042
8158
18194
200
application/javascript
Other
https://2girls1cup.ca/wp-content/uploads/2015/03/2girls1cupvideo.webm?_=1
h2
411.09599999618
562.24600004498
796
1048576
206
video/webm
Media
https://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/cv/result/783878fafd27b169
h2
956.59299998078
984.55199995078
883
2
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
58.898
12.52
98.115
16.981
119.268
5.041
124.323
25.525
150.059
5.162
158.311
18.973
188.022
8.852
203.211
21.121
224.347
58.06
671.981
285.842
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. 2girls1cup.ca should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 2girls1cup.ca should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 2girls1cup.ca should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 2girls1cup.ca should consider minifying JS files.
Reduce unused CSS — Potential savings of 16 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 2girls1cup.ca should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://2girls1cup.ca/wp-content/themes/twentysixteen/genericons/genericons.css
16605
16605
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 50 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://2girls1cup.ca/wp-content/uploads/2022/11/harlem-shake-poop.jpg
52314
23947.45
https://2girls1cup.ca/wp-content/uploads/2018/05/2-girls-1-cup-meme.jpg
47638
15427.5
https://2girls1cup.ca/wp-content/uploads/2015/03/2-girls-1-cup-logo.jpg
19137
12068.75
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 30 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://2girls1cup.ca/
27.865
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. 2girls1cup.ca should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://2girls1cup.ca/
190
https://2girls1cup.ca/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 2girls1cup.ca should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://2girls1cup.ca/wp-includes/js/mediaelement/mediaelement-and-player.min.js
54
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://2girls1cup.ca/wp-content/uploads/2015/03/2-girls-1-cup-logo.jpg
0
Uses efficient cache policy on static assets — 1 resource found
2girls1cup.ca 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://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1672704000
14400000
16019
Avoids an excessive DOM size — 106 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
106
Maximum DOM Depth
17
Maximum Child Elements
15
Avoid chaining critical requests — 18 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 2girls1cup.ca should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1672704000
291.485
279.057
2.061
https://2girls1cup.ca/
105.544
16.15
3.721
https://2girls1cup.ca/wp-includes/js/jquery/jquery.js
58.615
44.066
1.518
Unattributable
55.524
1.82
0
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
377.213
Other
76.783
Style & Layout
57.591
Parse HTML & CSS
17.418
Rendering
15.48
Script Parsing & Compilation
11.48
Garbage Collection
8.538
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 — 30 requests • 20,532 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
30
21025116
Media
3
20737814
Image
4
123396
Script
11
105423
Stylesheet
8
41794
Other
3
9750
Document
1
6939
Font
0
0
Third-party
2
423
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)
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.
Element
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
1.2177567638561E-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 — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1672704000
860
143
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of 2girls1cup.ca 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

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

Other

Eliminate render-blocking resources — Potential savings of 200 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. 2girls1cup.ca should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css
0
230
https://2girls1cup.ca/wp-content/themes/twentysixteen/genericons/genericons.css
16605
80
https://2girls1cup.ca/wp-includes/js/jquery/jquery.js
35593
80

Other

Avoid enormous network payloads — Total size was 20,532 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://2girls1cup.ca/wp-content/uploads/2015/03/2girls1cupvideo.mp4?_=1
10368513
https://2girls1cup.ca/wp-content/uploads/2015/03/2girls1cupvideo.mp4?_=1
10368505
https://2girls1cup.ca/wp-content/uploads/2022/11/harlem-shake-poop.jpg
53055
https://2girls1cup.ca/wp-content/uploads/2018/05/2-girls-1-cup-meme.jpg
48389
https://2girls1cup.ca/wp-includes/js/mediaelement/mediaelement-and-player.min.js
38548
https://2girls1cup.ca/wp-includes/js/jquery/jquery.js
35593
https://2girls1cup.ca/wp-content/uploads/2015/03/2-girls-1-cup-logo.jpg
19880
https://2girls1cup.ca/wp-content/themes/twentysixteen/genericons/genericons.css
16605
https://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1672704000
16019
https://2girls1cup.ca/wp-content/themes/twentysixteen/style.css
11723
89

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes 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.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

ARIA

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

Contrast

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

Navigation

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

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
67

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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
1.12.4
WordPress
5.1.15
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://2girls1cup.ca/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Uses deprecated APIs — 2 warnings found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
`window.webkitStorageInfo` is deprecated. Please use `navigator.webkitTemporaryStorage` or `navigator.webkitPersistentStorage` instead.
...
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
DOMException: play() can only be initiated by a user gesture.
DOMException: play() can only be initiated by a user gesture.
Failed to load resource: the server responded with a status of 404 (Not Found)
Refused to apply style from 'https://fonts.googleapis.com/css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Refused to apply style from 'https://fonts.googleapis.com/css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
100

SEO

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

Content Best Practices

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

Crawling and Indexing

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

Manual Checks

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

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 2girls1cup.ca. 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 2girls1cup.ca on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

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
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) 77
Performance 89
Accessibility 89
Best Practices 67
SEO 100
PWA 40
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://2girls1cup.ca/
Updated: 3rd January, 2023

1.73 seconds
First Contentful Paint (FCP)
77%
14%
9%

0.01 seconds
First Input Delay (FID)
88%
4%
8%

89

Performance

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

Metrics

Speed Index — 2.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.2 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 2.0 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://2girls1cup.ca/
http/1.1
0
48.081999993883
737
0
301
text/plain
https://2girls1cup.ca/
h2
48.549999948591
85.564999957569
6930
19428
200
text/html
Document
https://2girls1cup.ca/wp-includes/css/dist/block-library/style.min.css
h2
96.845999942161
125.10299996939
5046
25245
200
text/css
Stylesheet
https://2girls1cup.ca/wp-includes/css/dist/block-library/theme.min.css
h2
97.134000039659
157.03100000974
1132
1031
200
text/css
Stylesheet
https://fonts.googleapis.com/css
96.867999993265
109.03499997221
0
0
-1
Stylesheet
https://2girls1cup.ca/wp-content/themes/twentysixteen/genericons/genericons.css
h2
97.831999999471
111.68500001077
16597
26703
200
text/css
Stylesheet
https://2girls1cup.ca/wp-content/themes/twentysixteen/style.css
h2
97.996999975294
114.56100002397
11721
56498
200
text/css
Stylesheet
https://2girls1cup.ca/wp-content/themes/twentysixteen/css/blocks.css
h2
98.53600000497
124.09199995454
2204
6258
200
text/css
Stylesheet
https://2girls1cup.ca/wp-includes/js/jquery/jquery.js
h2
98.78200001549
119.64199994691
35587
96866
200
application/javascript
Script
https://2girls1cup.ca/wp-includes/js/jquery/jquery-migrate.min.js
h2
99.204999976791
112.46999993455
4819
10056
200
application/javascript
Script
https://2girls1cup.ca/wp-content/uploads/2015/03/2-girls-1-cup-logo.jpg
h2
185.36699994002
198.53499997407
19888
19137
200
image/jpeg
Image
https://2girls1cup.ca/wp-content/uploads/2018/05/2-girls-1-cup-meme.jpg
h2
185.67999999505
320.41099993512
48391
47638
200
image/jpeg
Image
https://2girls1cup.ca/wp-content/uploads/2022/11/harlem-shake-poop.jpg
h2
185.84499997087
199.25099995453
53065
52314
200
image/jpeg
Image
https://2girls1cup.ca/wp-includes/js/mediaelement/mediaelementplayer-legacy.min.css
h2
128.60699999146
144.15499998722
3276
11232
200
text/css
Stylesheet
https://2girls1cup.ca/wp-includes/js/mediaelement/wp-mediaelement.min.css
h2
145.76099999249
177.03100002836
1802
4163
200
text/css
Stylesheet
https://2girls1cup.ca/wp-content/themes/twentysixteen/js/skip-link-focus-fix.js
h2
158.60500000417
182.88400000893
1061
605
200
application/javascript
Script
https://2girls1cup.ca/wp-content/themes/twentysixteen/js/functions.js
h2
179.30099996738
198.12800001819
2176
4951
200
application/javascript
Script
https://2girls1cup.ca/wp-includes/js/wp-embed.min.js
h2
184.50700002722
320.98900002893
1424
1391
200
application/javascript
Script
https://2girls1cup.ca/wp-includes/js/mediaelement/mediaelement-and-player.min.js
h2
184.67999994755
203.60999996774
38550
156559
200
application/javascript
Script
https://2girls1cup.ca/wp-includes/js/mediaelement/mediaelement-migrate.min.js
h2
184.81499992777
197.66700000037
1256
1193
200
application/javascript
Script
https://2girls1cup.ca/wp-includes/js/mediaelement/wp-mediaelement.min.js
h2
184.96199999936
214.75699997973
1185
907
200
application/javascript
Script
https://2girls1cup.ca/wp-includes/js/mediaelement/renderers/vimeo.min.js
h2
185.14600000344
200.0410000328
2913
6170
200
application/javascript
Script
https://suborecho.com/cqDY9z6.bl2/5-lkSbWBQr9ANGDTUey/NDDygm5GNuC/0g0/NUTIIn0OOoDwkg1K
h2
186.01699999999
262.06099998672
423
0
404
text/plain
Script
data
197.12399994023
197.29499996174
0
715
200
image/png
Image
data
200.1600000076
200.27999999002
0
380
200
image/svg+xml
Image
https://2girls1cup.ca/wp-content/uploads/2015/03/2girls1cupvideo.mp4?_=1
227.29900002014
391.07599994168
0
0
-1
Media
data
234.25899993163
234.42300001625
0
547
200
image/svg+xml
Image
data
236.23199993744
236.36899993289
0
552
200
image/svg+xml
Image
data
238.42099995818
238.52000001352
0
177
200
image/svg+xml
Image
data
240.34300004132
240.46599993017
0
351
200
image/svg+xml
Image
data
242.02599993441
242.09800001699
0
242
200
image/svg+xml
Image
https://2girls1cup.ca/wp-includes/js/mediaelement/mejs-controls.svg
h2
379.41699998919
410.01799993683
2062
4598
200
image/svg+xml
Image
https://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1672704000
h2
409.77000002749
434.75300003774
15456
35374
200
application/javascript
Script
https://2girls1cup.ca/wp-content/uploads/2015/03/2girls1cupvideo.mp4?_=1
h2
413.39899995364
511.39599992894
10368507
1048576
206
video/mp4
Media
https://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/pica.js
h2
453.59399996232
466.75899997354
8791
19220
200
application/javascript
Other
https://2girls1cup.ca/wp-content/uploads/2015/03/2girls1cupvideo.webm?_=1
h2
518.06599996053
670.35099992063
811
1048576
206
video/webm
Media
https://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/cv/result/78387961cedbd9f5
h2
1142.416000017
1211.5520000225
877
2
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
90.094
16.883
160.294
19.762
180.79
9.112
189.914
28.126
218.751
10.598
232.985
17.112
254.677
7.352
324.927
27.013
353.675
36.856
440.036
7.13
849.153
294.861
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. 2girls1cup.ca should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 2girls1cup.ca should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 2girls1cup.ca should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 2girls1cup.ca should consider minifying JS files.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 40 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://2girls1cup.ca/
38.007
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. 2girls1cup.ca should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://2girls1cup.ca/
630
https://2girls1cup.ca/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 2girls1cup.ca should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://2girls1cup.ca/wp-includes/js/mediaelement/mediaelement-and-player.min.js
54
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Uses efficient cache policy on static assets — 1 resource found
2girls1cup.ca 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://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1672704000
14400000
15456
Avoids an excessive DOM size — 99 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
99
Maximum DOM Depth
17
Maximum Child Elements
15
Avoid chaining critical requests — 18 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 2girls1cup.ca should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 30 requests • 10,407 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
30
10656687
Media
3
10369318
Image
4
123406
Script
11
104850
Stylesheet
8
41778
Other
3
10405
Document
1
6930
Font
0
0
Third-party
2
423
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)
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
Below is a list of all DOM elements that contribute to the CLS of the page.
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 — 6 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1672704000
3810
590
https://2girls1cup.ca/wp-includes/js/jquery/jquery.js
2160
79
https://2girls1cup.ca/wp-includes/js/jquery/jquery.js
2610
74
https://2girls1cup.ca/
1110
68
https://2girls1cup.ca/
1189
56
https://2girls1cup.ca/wp-includes/js/mediaelement/mediaelement-and-player.min.js
2760
54
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of 2girls1cup.ca 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

First Contentful Paint — 2.0 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 4.0 s
The time taken for the page to become fully interactive.
Total Blocking Time — 330 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Eliminate render-blocking resources — Potential savings of 770 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. 2girls1cup.ca should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css
0
780
https://2girls1cup.ca/wp-content/themes/twentysixteen/genericons/genericons.css
16597
300
https://2girls1cup.ca/wp-content/themes/twentysixteen/style.css
11721
150
https://2girls1cup.ca/wp-includes/js/jquery/jquery.js
35587
300
https://2girls1cup.ca/wp-includes/js/jquery/jquery-migrate.min.js
4819
150
Reduce unused CSS — Potential savings of 26 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 2girls1cup.ca should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://2girls1cup.ca/wp-content/themes/twentysixteen/genericons/genericons.css
16597
16597
https://2girls1cup.ca/wp-content/themes/twentysixteen/style.css
11721
10375
Serve images in next-gen formats — Potential savings of 50 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://2girls1cup.ca/wp-content/uploads/2022/11/harlem-shake-poop.jpg
52314
23947.45
https://2girls1cup.ca/wp-content/uploads/2018/05/2-girls-1-cup-meme.jpg
47638
15427.5
https://2girls1cup.ca/wp-content/uploads/2015/03/2-girls-1-cup-logo.jpg
19137
12068.75
Reduce JavaScript execution time — 1.5 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://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1672704000
1219.98
1170.568
8.828
https://2girls1cup.ca/
418.244
59.22
16.612
Unattributable
234.5
6.636
0
https://2girls1cup.ca/wp-includes/js/jquery/jquery.js
222.832
167.124
9.776
https://2girls1cup.ca/wp-includes/js/mediaelement/mediaelement-and-player.min.js
88.044
68.664
10.768
Minimize main-thread work — 2.3 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
1513.576
Other
331.92
Style & Layout
218.612
Parse HTML & CSS
72.22
Rendering
52.42
Script Parsing & Compilation
50.272
Garbage Collection
33.66
First Contentful Paint (3G) — 4260 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Audits

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

Other

Avoid enormous network payloads — Total size was 10,407 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://2girls1cup.ca/wp-content/uploads/2015/03/2girls1cupvideo.mp4?_=1
10368507
https://2girls1cup.ca/wp-content/uploads/2022/11/harlem-shake-poop.jpg
53065
https://2girls1cup.ca/wp-content/uploads/2018/05/2-girls-1-cup-meme.jpg
48391
https://2girls1cup.ca/wp-includes/js/mediaelement/mediaelement-and-player.min.js
38550
https://2girls1cup.ca/wp-includes/js/jquery/jquery.js
35587
https://2girls1cup.ca/wp-content/uploads/2015/03/2-girls-1-cup-logo.jpg
19888
https://2girls1cup.ca/wp-content/themes/twentysixteen/genericons/genericons.css
16597
https://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1672704000
15456
https://2girls1cup.ca/wp-content/themes/twentysixteen/style.css
11721
https://2girls1cup.ca/cdn-cgi/challenge-platform/h/g/scripts/pica.js
8791
89

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes 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.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

ARIA

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

Contrast

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

Navigation

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

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
67

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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
1.12.4
WordPress
5.1.15
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://2girls1cup.ca/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Uses deprecated APIs — 2 warnings found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
`window.webkitStorageInfo` is deprecated. Please use `navigator.webkitTemporaryStorage` or `navigator.webkitPersistentStorage` instead.
...
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
DOMException: play() can only be initiated by a user gesture.
DOMException: play() can only be initiated by a user gesture.
Failed to load resource: the server responded with a status of 404 (Not Found)
Refused to apply style from 'https://fonts.googleapis.com/css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Refused to apply style from 'https://fonts.googleapis.com/css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for 2girls1cup.ca. 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 2girls1cup.ca on mobile screens.
Document uses legible font sizes — 93.51% 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
.mejs-cannotplay, .mejs-cannotplay a
6.37%
10.24px
.mejs-time
0.11%
11px
93.51%
≥ 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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

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

Manual Checks

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

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 2girls1cup.ca. 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 2girls1cup.ca on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

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
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: 172.67.152.55
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
Cloudflare, Inc.
Registration

Domain Registrant

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

Domain Registrar

Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Slightly Risky
WOT Rating:
WOT Trustworthiness: 80/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 17th June, 2022
Valid To: 17th 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: 11976726372308057528767967619483512641
Serial Number (Hex): 0902A2335281C7AF38D76A9B4A312F41
Valid From: 17th June, 2024
Valid To: 17th 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 17 00:38:06.303 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:E2:70:FD:B4:A5:1B:5E:38:4E:D7:18:
0E:04:FB:7F:8A:75:C3:38:3A:D0:97:28:4D:0A:39:A3:
C1:FF:B7:CF:5A:02:21:00:C4:2C:58:E8:9B:3B:27:52:
E4:2D:12:A3:A2:44:7F:DE:0A:19:40:F6:AB:A0:1D:52:
FC:CC:25:97:00:3D:C8:F7
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 17 00:38:06.326 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:90:F2:F6:F7:60:87:BF:A2:F2:79:F8:
D7:D0:39:15:3F:65:3F:A1:3D:16:D4:09:27:4E:52:50:
C9:F9:D4:1B:74:02:20:08:96:CF:2B:67:AA:81:28:34:
19:6C:F6:BA:EF:0C:66:93:80:6E:1D:EA:0B:2C:91:D3:
EE:A7:DC:55:DC:DA:93
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : Jun 17 00:38:06.358 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:06:B5:60:ED:B6:6B:03:D6:90:13:B0:15:
CF:80:71:C1:C2:48:AD:A7:BE:9B:BD:DC:6B:32:43:EB:
CB:A6:73:3C:02:21:00:C9:67:02:9E:2F:22:45:0C:80:
3C:89:8C:1B:80:85:5F:10:FF:85:D0:3A:59:CB:51:E8:
DE:53:83:D4:06:EF:11
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:2girls1cup.ca
DNS:sni.cloudflaressl.com
DNS:*.2girls1cup.ca
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 3rd January, 2023
Content-Type: text/html; charset=UTF-8
Cache-Control: max-age=16070400
Server: cloudflare
Connection: keep-alive
Vary: Accept-Encoding
X-Powered-By: PHP/5.4.45
Link: <https://2girls1cup.ca/wp-json/>; rel="https://api.w.org/", <https://2girls1cup.ca/>; rel=shortlink
X-Cache: HIT from Backend
CF-Cache-Status: HIT
Age: 430091
Last-Modified: 29th December, 2022
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=P7%2F%2FthMo%2FKWntkk5yKXdDgfnPaU43GY3J5Cxv0nD3zuMDV1cfR0za4gdIEH2jZIl1o8zwg2qogynprtmivYMYAcb%2BFukZ7%2BIcseuTjZYd3px7eKKBxoN%2BYnOi8y7WdfL"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 783878d929ce8c78-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers:
Full Whois:

Nameservers

Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$765 USD 1/5
0/5
$399 USD 1/5
0/5

Sites hosted on the same IP address