cam4.es

cam4.es is SSL secured

Free website and domain report on cam4.es

Last Updated: 14th October, 2022 Update Now
Overview

Snoop Summary for cam4.es

This is a free and comprehensive report about cam4.es. Cam4.es is hosted in United States on a server with an IP address of 184.94.152.23, where USD is the local currency and the local language is English. Our records indicate that cam4.es is owned/operated by Surecom Corporation N.V.. Cam4.es is expected to earn an estimated $1,066 USD per day from advertising revenue. The sale of cam4.es would possibly be worth $777,922 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Cam4.es is insanely popular with an estimated 169,824 daily unique visitors. This report was last updated 14th October, 2022.

About cam4.es

Site Preview:
Title: Cam4 Free Live Sex Cams, Adult Sex Chat ❤️ Naked Pornstar Cams | CAM4.com
Description: Watch Real People Naked & Having Sex Live on Webcam 24/7. 100% Free to Watch, Chat & Broadcast. No-Sign Up & No Registration Required.
Keywords and Tags: adult content, andreahsexy cam4, cam4, cam4 com, cam4 es, cam4es, cam4ç, chat gay en vivo, gays en vivo, perlalovers, popular, porno en directo, porno gratis, pornography, sexo cam, videos sexo en directo
Related Terms: cam4 chat, cam4 outdoor live videos, cam4.com, camvault cam4, funfitness cam4, rebysexy cam4, sexy minee cam4, www cam4 com
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

3/5 (Great!)

Valuation

$777,922 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 9,307
Alexa Reach:
SEMrush Rank (US): 289,247
SEMrush Authority Score: 44
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 2,511 0
Traffic: 4,637 0
Cost: $1,780 USD $0 USD
Traffic

Visitors

Daily Visitors: 169,824
Monthly Visitors: 5,168,906
Yearly Visitors: 61,985,741
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1,066 USD
Monthly Revenue: $32,434 USD
Yearly Revenue: $388,956 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 153,821
Referring Domains: 1,157
Referring IPs: 632
Cam4.es has 153,821 backlinks according to SEMrush. 97% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve cam4.es's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of cam4.es's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://susupetalos.es/posts/page/16/
Target: http://www.cam4.es/

2
Source: https://carlahetaira.blogspot.com/2018/01/puedo-ser-puta.html
Target: https://www.cam4.es/shemale

3
Source: https://carlahetaira.blogspot.com/2018/01/puedo-ser-puta.html
Target: https://www.cam4.es/shemale

4
Source: https://carlahetaira.blogspot.com/2018/07/el-lunes-siguiente.html
Target: https://www.cam4.es/shemale

5
Source: https://carlahetaira.blogspot.com/2018/07/el-lunes-siguiente.html
Target: https://www.cam4.es/shemale

Top Ranking Keywords (US)

1
Keyword: porno gratis
Ranked Page: https://www.cam4.es/

2
Keyword: cam4 es
Ranked Page: https://www.cam4.es/

3
Keyword: chat gay en vivo
Ranked Page: https://www.cam4.es/male/gay

4
Keyword: perlalovers
Ranked Page: https://www.cam4.es/blog/perlalovers-la-chica-webcam-de-la-semana-en-cam4/

5
Keyword: cam4
Ranked Page: https://www.cam4.es/

Domain Analysis

Value Length
Domain: cam4.es 7
Domain Name: cam4 4
Extension (TLD): es 2

Page Speed Analysis

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

PageSpeed Insights

Avg. (All Categories) 81
Performance 96
Accessibility 94
Best Practices 92
SEO 100
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.cam4.com/
Updated: 14th October, 2022

2.67 seconds
First Contentful Paint (FCP)
61%
19%
20%

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

96

Performance

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

Metrics

First Contentful Paint — 0.9 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 — 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
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 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://cam4.es/
http/1.1
0
35.672000143677
247
0
301
text/html
https://cam4.es/
http/1.1
36.104999948293
158.04299991578
224
0
301
text/plain
https://www.cam4.es/
http/1.1
158.48799981177
229.76600006223
213
0
302
text/plain
https://www.cam4.com/
h2
230.01600010321
350.83199990913
60655
229028
200
text/html
Document
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=466fa1aa-ce2e-4b71-b329-6cd08d681302
h2
364.25499990582
368.68100007996
4976
4535
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-P5TFR9Z
h2
372.16300005093
399.71899986267
66472
193928
200
application/javascript
Script
https://dumpster.cam4.com/v2/directory.js
h2
373.40100016445
461.37600019574
15348
70125
200
application/javascript
Script
https://dev.visualwebsiteoptimizer.com/j.php?a=287192&u=https%3A%2F%2Fwww.cam4.com%2F&f=1&r=0.2771388933078607
h2
379.76100016385
396.82399993762
5440
16416
200
application/javascript
Script
data
381.11800001934
381.24899985269
0
2041
200
image/png
Image
data
381.38000015169
381.47700019181
0
1576
200
image/png
Image
data
381.59300014377
381.71300012618
0
2258
200
image/png
Image
data
381.91499980167
382.00799981132
0
1124
200
image/gif
Image
data
382.22499983385
382.48400017619
0
6726
200
image/png
Image
data
386.30700018257
386.39400014654
0
289
200
image/png
Image
data
415.23599997163
415.46100005507
0
1774
200
image/png
Image
data
426.89399980009
427.24099988118
0
4934
200
image/png
Image
data
430.00799976289
430.38900010288
0
6276
200
image/png
Image
https://dev.visualwebsiteoptimizer.com/7.0/va-573dbaa3a36312bdee7d425b79f55556.js
h2
500.47799991444
526.80600015447
65981
231875
200
text/javascript
Script
https://dev.visualwebsiteoptimizer.com/v.gif?cd=0&a=287192&d=cam4.com&u=D1E7601F5F06BAFF0B8040D9463035049&h=16caff6c52d7cc2fd3be55f0a70d8f80&t=false&r=0.8405630280017351
h2
501.21300015599
532.27799991146
353
0
200
application/javascript
Image
https://cam4.firebaseio.com/?q=1665728475051
http/1.1
541.39199992642
660.35299981013
433
0
301
text/plain
https://dumpster.cam4.com/v2/snpl.js
h2
542.33699990436
625.45799976215
24893
74309
200
application/javascript
Script
https://d35tca7vmefkrc.cloudfront.net/scripts/5fda2e5596da8516d0ffb8d7.js
h2
558.32999991253
580.12099983171
5090
13650
200
application/x-javascript
Script
https://static.hotjar.com/c/hotjar-41393.js?sv=7
h2
572.33100011945
580.53700020537
3387
6228
200
application/javascript
Script
https://logger007.cam4.com/v2/analytics/ui
587.20100019127
591.05699975044
0
0
-1
Ping
https://script.hotjar.com/modules.bcd9ade6b0bb9bdd0789.js
h2
594.37400009483
601.77200008184
66963
260588
200
application/javascript
Script
https://console.firebase.google.com/project/project-6798047017169985057/database/cam4/data/
660.35299981013
660.90600006282
0
0
-1
Fetch
https://dev.visualwebsiteoptimizer.com/settings.js?a=287192&settings_type=1&vn=7.0&exc=230|231
h2
671.31699994206
686.54699996114
999
1198
200
application/javascript
Script
https://vars.hotjar.com/box-69edcc3187336f9b0a3fbb4c73be9fe6.html
h2
681.47499999031
685.60899980366
1710
2431
200
text/html
Document
https://api.cam4.com/gloryhole/com.snowplowanalytics.snowplow/tp2
h2
822.38199980929
890.96200000495
304
0
200
Preflight
https://api.cam4.com/gloryhole/com.snowplowanalytics.snowplow/tp2
h2
891.65600016713
935.9659999609
395
2
200
text/plain
XHR
https://d28x3y4m87xprs.cloudfront.net/f.5fda2e5596da8516d0ffb8d7?nv=0&ns=0&ib=0&v=ydZAVkOIwyJZCuVi&s=ydZAVkOIwyJZCuViMQT5KmxsivtArEPZ&en=_fxm.pages.view&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_15_7)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F98.0.4695.0%20Safari%2F537.36%20Chrome-Lighthouse&hn=www.cam4.com&url=https%3A%2F%2Fwww.cam4.com%2F&ref=&pn=%2F&pt=Cam4%20Free%20Live%20Sex%20Cams%2C%20Adult%20Sex%20Chat%20%E2%9D%A4%EF%B8%8F%20Naked%20Pornstar%20Cams%20%7C%20CAM4.com&sr=800x600&bw=1350&bh=940&tzo=420&tz=-7&tzn=PST8PDT&lng=en-US&ce=true&im=0&tech_cd=24&tech_pd=24&cb=1665728475346&perf_pd=803.90&perf_dr=415.10&perf_pr=803.90
h2
837.64600008726
853.70399989188
475
43
200
image/gif
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)
356.759
13.872
371.594
12.97
384.575
18.425
407.74
31.686
440.065
56.631
496.939
5.094
502.775
17.995
521.045
11.334
532.45
11.277
543.745
40.117
597.523
12.871
611.801
47.934
661.559
6.453
676.501
62.492
740.761
7.59
754.392
7.267
764.816
40.779
808.407
6.499
815.662
8.313
823.987
8.385
832.947
5.901
839.85
11.342
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

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Cam4.es should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 6 KiB
Images can slow down the page's load time. Cam4.es should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
6726
6315
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Cam4.es should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Cam4.es should consider minifying CSS files.
Minify JavaScript — Potential savings of 6 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Cam4.es should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://dumpster.cam4.com/v2/directory.js
15348
6372
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Cam4.es should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 110 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://script.hotjar.com/modules.bcd9ade6b0bb9bdd0789.js
66963
45133
https://dev.visualwebsiteoptimizer.com/7.0/va-573dbaa3a36312bdee7d425b79f55556.js
65981
39170
https://www.googletagmanager.com/gtm.js?id=GTM-P5TFR9Z
66472
28162
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.cam4.com/
121.809
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Cam4.es 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://script.hotjar.com/modules.bcd9ade6b0bb9bdd0789.js
48
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 317 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://script.hotjar.com/modules.bcd9ade6b0bb9bdd0789.js
66963
https://www.googletagmanager.com/gtm.js?id=GTM-P5TFR9Z
66472
https://dev.visualwebsiteoptimizer.com/7.0/va-573dbaa3a36312bdee7d425b79f55556.js
65981
https://www.cam4.com/
60655
https://dumpster.cam4.com/v2/snpl.js
24893
https://dumpster.cam4.com/v2/directory.js
15348
https://dev.visualwebsiteoptimizer.com/j.php?a=287192&u=https%3A%2F%2Fwww.cam4.com%2F&f=1&r=0.2771388933078607
5440
https://d35tca7vmefkrc.cloudfront.net/scripts/5fda2e5596da8516d0ffb8d7.js
5090
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=466fa1aa-ce2e-4b71-b329-6cd08d681302
4976
https://static.hotjar.com/c/hotjar-41393.js?sv=7
3387
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Cam4.es should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.cam4.com/
149.968
7.004
1.812
https://dumpster.cam4.com/v2/directory.js
85.348
79.755
1.304
https://www.googletagmanager.com/gtm.js?id=GTM-P5TFR9Z
73.43
60.096
7.516
https://script.hotjar.com/modules.bcd9ade6b0bb9bdd0789.js
72.966
62.823
5.318
https://dev.visualwebsiteoptimizer.com/7.0/va-573dbaa3a36312bdee7d425b79f55556.js
62.945
56.639
3.194
Minimizes main-thread work — 0.5 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
303.821
Style & Layout
88.774
Other
60.586
Script Parsing & Compilation
23.057
Rendering
22.375
Parse HTML & CSS
20.352
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 — 22 requests • 317 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
22
324558
Script
9
254573
Document
2
62365
Image
3
5804
Other
8
1816
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
16
222963
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)
72773
0
72060
0
66472
0
4976
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
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
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 cam4.es 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.3 s
The timing of the largest text or image that is painted.

Other

Avoid multiple page redirects — Potential savings of 570 ms
Redirects can cause additional delays before the page can begin loading. Cam4.es should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://cam4.es/
190
https://cam4.es/
150
https://www.cam4.es/
230
https://www.cam4.com/
0
Serve static assets with an efficient cache policy — 8 resources found
Cam4.es 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://d35tca7vmefkrc.cloudfront.net/scripts/5fda2e5596da8516d0ffb8d7.js
0
5090
https://d28x3y4m87xprs.cloudfront.net/f.5fda2e5596da8516d0ffb8d7?nv=0&ns=0&ib=0&v=ydZAVkOIwyJZCuVi&s=ydZAVkOIwyJZCuViMQT5KmxsivtArEPZ&en=_fxm.pages.view&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_15_7)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F98.0.4695.0%20Safari%2F537.36%20Chrome-Lighthouse&hn=www.cam4.com&url=https%3A%2F%2Fwww.cam4.com%2F&ref=&pn=%2F&pt=Cam4%20Free%20Live%20Sex%20Cams%2C%20Adult%20Sex%20Chat%20%E2%9D%A4%EF%B8%8F%20Naked%20Pornstar%20Cams%20%7C%20CAM4.com&sr=800x600&bw=1350&bh=940&tzo=420&tz=-7&tzn=PST8PDT&lng=en-US&ce=true&im=0&tech_cd=24&tech_pd=24&cb=1665728475346&perf_pd=803.90&perf_dr=415.10&perf_pr=803.90
0
475
https://dev.visualwebsiteoptimizer.com/v.gif?cd=0&a=287192&d=cam4.com&u=D1E7601F5F06BAFF0B8040D9463035049&h=16caff6c52d7cc2fd3be55f0a70d8f80&t=false&r=0.8405630280017351
0
353
https://dumpster.cam4.com/v2/directory.js
60000
15348
https://static.hotjar.com/c/hotjar-41393.js?sv=7
60000
3387
https://dumpster.cam4.com/v2/snpl.js
86400000
24893
https://dev.visualwebsiteoptimizer.com/7.0/va-573dbaa3a36312bdee7d425b79f55556.js
604800000
65981
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=466fa1aa-ce2e-4b71-b329-6cd08d681302
2592000000
4976

Other

Avoid an excessive DOM size — 1,578 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
1578
Maximum DOM Depth
15
Maximum Child Elements
73
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://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=466fa1aa-ce2e-4b71-b329-6cd08d681302
94

Accessibility

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

Navigation

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 cam4.es 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
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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://dumpster.cam4.com/v2/snpl.js
https://dumpster.cam4.com/v2/sp.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://cam4.es/
Allowed
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for cam4.es. 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 cam4.es 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.
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 cam4.es. 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 cam4.es 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) 74
Performance 72
Accessibility 94
Best Practices 75
SEO 100
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.cam4.com/
Updated: 14th October, 2022

3.00 seconds
First Contentful Paint (FCP)
50%
25%
25%

0.02 seconds
First Input Delay (FID)
94%
4%
2%

72

Performance

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

Metrics

Total Blocking Time — 120 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://cam4.es/
http/1.1
0
53.847000002861
232
0
301
text/html
https://cam4.es/
http/1.1
54.131000011694
346.77299996838
224
0
301
text/plain
https://www.cam4.es/
http/1.1
347.02799998922
428.61599999014
213
0
302
text/plain
https://www.cam4.com/
h2
428.9090000093
579.91299999412
60655
229028
200
text/html
Document
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=466fa1aa-ce2e-4b71-b329-6cd08d681302
h2
592.36999996938
609.32899999898
4976
4535
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-P5TFR9Z
h2
595.84700001869
633.7240000139
66439
193918
200
application/javascript
Script
https://dumpster.cam4.com/v2/directory.js
h2
601.428999973
698.01699998789
15348
70125
200
application/javascript
Script
https://dev.visualwebsiteoptimizer.com/j.php?a=287192&u=https%3A%2F%2Fwww.cam4.com%2F&f=1&r=0.625846434635259
h2
601.56799998367
625.72900002124
5536
16443
200
application/javascript
Script
data
602.41399996448
602.57499996806
0
2041
200
image/png
Image
data
602.71000000648
602.81399998348
0
1576
200
image/png
Image
data
602.92899998603
603.05500001414
0
2258
200
image/png
Image
data
603.21999998996
603.29499997897
0
1124
200
image/gif
Image
data
603.4750000108
603.71499997564
0
6726
200
image/png
Image
data
633.84700001916
634.08899999922
0
4934
200
image/png
Image
https://dev.visualwebsiteoptimizer.com/web/djIkdGU6Ny4wOmFzeW5jJWpxdWVyeQ==/tag-253bec39360da1ac5cdb76958ef8456c.js
h2
669.19799998868
708.64999998594
66032
231901
200
text/javascript
Script
https://dev.visualwebsiteoptimizer.com/v.gif?cd=0&a=287192&d=cam4.com&u=DADC924063A44018F1F66A9668C8A1309&h=90d73c59ec6989c1b64ee40db6c8a4a8&t=false&r=0.5488825217469182
h2
669.69999996945
695.47299999977
353
0
200
application/javascript
Image
https://d35tca7vmefkrc.cloudfront.net/scripts/5fda2e5596da8516d0ffb8d7.js
h2
701.56600000337
748.22499998845
5090
13650
200
application/x-javascript
Script
https://static.hotjar.com/c/hotjar-41393.js?sv=7
h2
709.88199999556
722.24799997639
3386
6227
200
application/javascript
Script
https://cam4.firebaseio.com/?q=1665728494532
http/1.1
724.0270000184
818.3410000056
418
0
301
text/plain
https://dumpster.cam4.com/v2/snpl.js
h2
724.60899996804
770.65700001549
24893
74309
200
application/javascript
Script
https://logger007.cam4.com/v2/analytics/ui
726.22599999886
729.30700000143
0
0
-1
Ping
https://script.hotjar.com/modules.bcd9ade6b0bb9bdd0789.js
h2
728.17399998894
742.98199999612
66963
260588
200
application/javascript
Script
https://dev.visualwebsiteoptimizer.com/settings.js?a=287192&settings_type=1&vn=7.0&exc=230|231
h2
765.93499997398
790.10300000664
1227
1666
200
application/javascript
Script
https://vars.hotjar.com/box-69edcc3187336f9b0a3fbb4c73be9fe6.html
h2
816.37600000249
828.15899996785
1710
2431
200
text/html
Document
https://console.firebase.google.com/project/project-6798047017169985057/database/cam4/data/
818.3410000056
818.75400000717
0
0
-1
Fetch
https://api.cam4.com/gloryhole/com.snowplowanalytics.snowplow/tp2
h2
875.3859999706
960.00899997307
304
0
200
Preflight
https://api.cam4.com/gloryhole/com.snowplowanalytics.snowplow/tp2
h2
960.39999998175
1068.1270000059
395
2
200
text/plain
XHR
https://d28x3y4m87xprs.cloudfront.net/f.5fda2e5596da8516d0ffb8d7?nv=0&ns=0&ib=0&v=y8E12UPTKQ8TiNOy&s=y8E12UPTKQ8TiNOyKwKBFbEgTFEl38UQ&en=_fxm.pages.view&ua=Mozilla%2F5.0%20(Linux%3B%20Android%207.0%3B%20Moto%20G%20(4))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F98.0.4695.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&hn=www.cam4.com&url=https%3A%2F%2Fwww.cam4.com%2F&ref=&pn=%2F&pt=Cam4%20Free%20Live%20Sex%20Cams%2C%20Adult%20Sex%20Chat%20%E2%9D%A4%EF%B8%8F%20Naked%20Pornstar%20Cams%20%7C%20CAM4.com&sr=360x640&bw=360&bh=640&tzo=420&tz=-7&tzn=PST8PDT&lng=en-US&ce=true&im=1&tech_cd=24&tech_pd=24&cb=1665728494693&perf_pd=863.80&perf_dr=630.80&perf_pr=863.80
h2
886.52699999511
914.57299998729
475
43
200
image/gif
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)
584.426
11.09
595.788
10.123
605.923
14.384
626.02
12.873
639.544
27.258
678.298
10.077
688.389
5.344
693.769
22.541
720.343
5.674
731.683
31.264
768.236
8.62
777.645
33.726
824.245
7.062
832.472
6.125
840.343
24.695
871.515
5.543
877.086
5.569
1023.742
7.821
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

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Cam4.es should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 4 KiB
Images can slow down the page's load time. Cam4.es should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
6726
4185
Defer offscreen images — Potential savings of 9 KiB
Time to Interactive can be slowed down by resources on the page. Cam4.es should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
4934
4934
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=466fa1aa-ce2e-4b71-b329-6cd08d681302
4535
4535
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Cam4.es should consider minifying CSS files.
Minify JavaScript — Potential savings of 6 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Cam4.es should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://dumpster.cam4.com/v2/directory.js
15348
6372
Reduce unused CSS — Potential savings of 11 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Cam4.es 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)
/*! normalize.css v7.0.0 | MIT License | github.com/necolas/normalize.css */html{line-height:1.15; ... } ...
17201
10904
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 150 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.cam4.com/
151.997
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Cam4.es 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://script.hotjar.com/modules.bcd9ade6b0bb9bdd0789.js
48
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 317 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://script.hotjar.com/modules.bcd9ade6b0bb9bdd0789.js
66963
https://www.googletagmanager.com/gtm.js?id=GTM-P5TFR9Z
66439
https://dev.visualwebsiteoptimizer.com/web/djIkdGU6Ny4wOmFzeW5jJWpxdWVyeQ==/tag-253bec39360da1ac5cdb76958ef8456c.js
66032
https://www.cam4.com/
60655
https://dumpster.cam4.com/v2/snpl.js
24893
https://dumpster.cam4.com/v2/directory.js
15348
https://dev.visualwebsiteoptimizer.com/j.php?a=287192&u=https%3A%2F%2Fwww.cam4.com%2F&f=1&r=0.625846434635259
5536
https://d35tca7vmefkrc.cloudfront.net/scripts/5fda2e5596da8516d0ffb8d7.js
5090
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=466fa1aa-ce2e-4b71-b329-6cd08d681302
4976
https://static.hotjar.com/c/hotjar-41393.js?sv=7
3386
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Cam4.es 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.7 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.cam4.com/
350.864
21.524
6.024
https://dumpster.cam4.com/v2/directory.js
230.928
211.924
2.904
https://www.googletagmanager.com/gtm.js?id=GTM-P5TFR9Z
174.168
145.996
15.816
https://script.hotjar.com/modules.bcd9ade6b0bb9bdd0789.js
168.072
150.924
8.32
https://dev.visualwebsiteoptimizer.com/web/djIkdGU6Ny4wOmFzeW5jJWpxdWVyeQ==/tag-253bec39360da1ac5cdb76958ef8456c.js
158.868
147.52
5.424
Unattributable
85.68
8.38
0.592
Minimizes main-thread work — 1.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
792.752
Other
188.196
Style & Layout
186.556
Parse HTML & CSS
53.8
Script Parsing & Compilation
47.52
Rendering
45.476
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 — 22 requests • 317 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
22
324869
Script
9
254914
Document
2
62365
Image
3
5804
Other
8
1786
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
16
223274
Minimize third-party usage — Third-party code blocked the main thread for 130 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)
73148
65.732
72059
56.336
66439
6.148
4976
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 — 5 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://dev.visualwebsiteoptimizer.com/web/djIkdGU6Ny4wOmFzeW5jJWpxdWVyeQ==/tag-253bec39360da1ac5cdb76958ef8456c.js
5314
125
https://www.googletagmanager.com/gtm.js?id=GTM-P5TFR9Z
5224
90
https://script.hotjar.com/modules.bcd9ade6b0bb9bdd0789.js
7333
67
https://www.cam4.com/
630
55
https://www.cam4.com/
3083
51
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 cam4.es 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

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

Audits

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

Other

Serve static assets with an efficient cache policy — 7 resources found
Cam4.es 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://d35tca7vmefkrc.cloudfront.net/scripts/5fda2e5596da8516d0ffb8d7.js
0
5090
https://d28x3y4m87xprs.cloudfront.net/f.5fda2e5596da8516d0ffb8d7?nv=0&ns=0&ib=0&v=y8E12UPTKQ8TiNOy&s=y8E12UPTKQ8TiNOyKwKBFbEgTFEl38UQ&en=_fxm.pages.view&ua=Mozilla%2F5.0%20(Linux%3B%20Android%207.0%3B%20Moto%20G%20(4))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F98.0.4695.0%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse&hn=www.cam4.com&url=https%3A%2F%2Fwww.cam4.com%2F&ref=&pn=%2F&pt=Cam4%20Free%20Live%20Sex%20Cams%2C%20Adult%20Sex%20Chat%20%E2%9D%A4%EF%B8%8F%20Naked%20Pornstar%20Cams%20%7C%20CAM4.com&sr=360x640&bw=360&bh=640&tzo=420&tz=-7&tzn=PST8PDT&lng=en-US&ce=true&im=1&tech_cd=24&tech_pd=24&cb=1665728494693&perf_pd=863.80&perf_dr=630.80&perf_pr=863.80
0
475
https://dev.visualwebsiteoptimizer.com/v.gif?cd=0&a=287192&d=cam4.com&u=DADC924063A44018F1F66A9668C8A1309&h=90d73c59ec6989c1b64ee40db6c8a4a8&t=false&r=0.5488825217469182
0
353
https://dumpster.cam4.com/v2/directory.js
60000
15348
https://static.hotjar.com/c/hotjar-41393.js?sv=7
60000
3386
https://dumpster.cam4.com/v2/snpl.js
86400000
24893
https://images.dmca.com/Badges/_dmca_premi_badge_4.png?ID=466fa1aa-ce2e-4b71-b329-6cd08d681302
2592000000
4976

Metrics

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

Other

Reduce unused JavaScript — Potential savings of 110 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://script.hotjar.com/modules.bcd9ade6b0bb9bdd0789.js
66963
45133
https://dev.visualwebsiteoptimizer.com/web/djIkdGU6Ny4wOmFzeW5jJWpxdWVyeQ==/tag-253bec39360da1ac5cdb76958ef8456c.js
66032
39044
https://www.googletagmanager.com/gtm.js?id=GTM-P5TFR9Z
66439
28149
Avoid multiple page redirects — Potential savings of 1,890 ms
Redirects can cause additional delays before the page can begin loading. Cam4.es should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://cam4.es/
630
https://cam4.es/
480
https://www.cam4.es/
780
https://www.cam4.com/
0
Avoid an excessive DOM size — 1,578 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
1578
Maximum DOM Depth
15
Maximum Child Elements
73
First Contentful Paint (3G) — 5889 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
94

Accessibility

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

Navigation

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that cam4.es 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
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.
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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://dumpster.cam4.com/v2/snpl.js
https://dumpster.cam4.com/v2/sp.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://cam4.es/
Allowed

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
96 x 23 (4.17)
433 x 93 (4.66)
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
65 x 23
87 x 31
130 x 46
65 x 23
88 x 31
130 x 46
61 x 23
80 x 30
122 x 46
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for cam4.es. 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 cam4.es on mobile screens.
Document uses legible font sizes — 85.68% 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
.Thumbnail__thumbnail__1H7vm .Thumbnail__performerInfo__i0s7O
2.76%
11px
11.56%
< 12px
85.68%
≥ 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.
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 cam4.es. 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 cam4.es 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: 184.94.152.23
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

Registration

Domain Registrant

Private Registration: No
Name:
Organization: Surecom Corporation N.V.
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: Safe
WOT Rating:
WOT Trustworthiness: 80/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: only-livecams.com
Issued By: GlobalSign RSA OV SSL CA 2018
Valid From: 21st October, 2021
Valid To: 22nd November, 2022
Subject: CN = only-livecams.com
O = Surecom Corporation N.V.
L = Willemstad
S = CW
Hash: 75f3c514
Issuer: CN = GlobalSign RSA OV SSL CA 2018
O = GlobalSign nv-sa
S = BE
Version: 2
Serial Number: 30520741031476368752755283622
Serial Number (Hex): 629E2A4E9C15CE2C344F16A6
Valid From: 21st October, 2024
Valid To: 22nd November, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:F8:EF:7F:F2:CD:78:67:A8:DE:6F:8F:24:8D:88:F1:87:03:02:B3:EB
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.globalsign.com/gsrsaovsslca2018.crl

Certificate Policies: Policy: 1.3.6.1.4.1.4146.1.20
CPS: https://www.globalsign.com/repository/
Policy: 2.23.140.1.2.2

Authority Information Access: CA Issuers - URI:http://secure.globalsign.com/cacert/gsrsaovsslca2018.crt
OCSP - URI:http://ocsp.globalsign.com/gsrsaovsslca2018

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Oct 21 20:24:08.631 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:86:BA:28:0F:19:1C:E4:2A:AD:C6:61:
A9:81:D3:55:36:FA:06:26:AD:30:3B:46:49:40:9E:7C:
D3:5B:DC:7B:BB:02:20:66:DB:29:5B:30:C7:77:BD:A2:
51:6D:BB:57:25:DB:90:F9:5F:D7:2E:EC:7D:42:1E:DF:
93:1F:F2:76:EC:3C:8E
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Oct 21 20:24:08.623 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:6C:49:2D:1B:DF:08:DF:C9:E8:F2:E1:93:
B4:53:27:67:A7:AF:A3:2C:49:DD:4B:61:68:6A:DF:5B:
1C:EE:52:5D:02:20:79:EE:EC:9D:7D:55:5A:84:58:92:
51:26:88:CE:D7:9E:07:F2:BD:44:D3:8B:AD:71:97:D0:
68:5A:AC:21:25:70
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 51:A3:B0:F5:FD:01:79:9C:56:6D:B8:37:78:8F:0C:A4:
7A:CC:1B:27:CB:F7:9E:88:42:9A:0D:FE:D4:8B:05:E5
Timestamp : Oct 21 20:24:08.666 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:26:98:AE:EF:C5:95:77:2E:78:44:66:72:
38:DD:EB:10:68:1E:D3:F2:3D:66:F5:7F:A6:B0:B5:7F:
9D:9E:12:51:02:21:00:92:B5:49:42:64:27:66:FE:55:
39:C6:B0:E2:43:34:A4:13:4D:6A:44:25:61:C8:6A:76:
DB:44:36:75:45:A7:1C
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:cam4.de.com
DNS:cam4.es
DNS:cam4.fr
DNS:www.cam4.de.com
DNS:www.cam4.es
DNS:www.cam4.fr
DNS:www.only-livecams.com
DNS:only-livecams.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 301 Moved Permanently
Server: nginx
Date: 14th October, 2022
Content-Length: 0
Connection: keep-alive
location: https://www.cam4.es/

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: dns1.p04.nsone.net
dns2.p04.nsone.net
dns3.p04.nsone.net
dns4.p04.nsone.net
Full Whois:
Conditions of use for the whois service via port 43 for .es domains

Access will only be enabled for IP addresses authorised by Red.es. A maximum of one IP address per
user/organisation is permitted.

Red.es accepts no responsibility whatsoever for the availability of access to WHOIS, which may be
suspended at any time and without prior warning at the discretion of the public entity.

The service will be limited to the data established by Red.es.

The user promises to make use of the service and to carry out any action derived from the aforesaid
use in accordance with current applicable regulations, in particular with legislation on “.es” domain
names and personal data protection.

In particular, the user undertakes not to use the service to carry out abusive or speculative domain
name registrations, pursuant to section 5 of the Sixth Additional Provision of Law 34/2002, of 11 July,
on Services of the Information Society and Electronic Commerce. Likewise, the User undertakes not to
use the service to obtain data, the possession of which may contravene the provisions of Organic Law
15/1999, of 13 December, on Personal Data Protection, and its Regulations, or in Law 34/2002, of 11
July, on Services of the Information Society and Electronic Commerce.

Failure to comply with these conditions will result in the immediate withdrawal of the service and any
registered domain name which breaches said conditions may be officially cancelled by Red.es.
-------------------------------------------------------------------------------------------------------

The IP address used to perform the query is not authorised or has exceeded the established limit for
queries.To request access to the service,complete the form located at https://sede.red.gob.es/sede/whois,
where you may also consult the service conditions.

-------------------------------------------------------------------------------------------------------
More information on each domain may be consulted at www.dominios.es.

Nameservers

Name IP Address
dns1.p04.nsone.net 198.51.44.4
dns2.p04.nsone.net 198.51.45.4
dns3.p04.nsone.net 198.51.44.68
dns4.p04.nsone.net 198.51.45.68
Related

Subdomains

Domain Subdomain
es

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$10,685,430 USD 5/5
0/5
$750 USD
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$10,685,430 USD 5/5
$221,189 USD 3/5