mycima.tube

mycima.tube is SSL secured

Free website and domain report on mycima.tube

Last Updated: 21st June, 2022
Overview

Snoop Summary for mycima.tube

This is a free and comprehensive report about mycima.tube. The domain mycima.tube is currently hosted on a server located in United States with the IP address 104.21.86.108, where the local currency is USD and English is the local language. Our records indicate that mycima.tube is privately registered by eng. Mycima.tube is expected to earn an estimated $1,647 USD per day from advertising revenue. The sale of mycima.tube would possibly be worth $1,202,616 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Mycima.tube is insanely popular with an estimated 262,538 daily unique visitors. This report was last updated 21st June, 2022.

About mycima.tube

Site Preview: mycima.tube mycima.tube
Title: مشاهدة ماى سيما MYCIMA افلام و مسلسلات اون لاين - ماي سيما
Description: موقع ماى سيما MYCIMA مشاهدة الافلام مباشرة افلام ومسلسلات مشاهدة مباشرة اون لاين عربى واجنبى افلام مترجمة ومسلسلات مترجمة ماى سينما
Keywords:
Popular Terms:
Fav Icon:
Tags and Categories: blogs, wiki
Age: Over 1 year old
Domain Created: 18th December, 2020
Domain Updated: 29th December, 2021
Domain Expires: 18th December, 2022
Review

Snoop Score

3/5 (Great!)

Valuation

$1,202,616 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 7,148
Alexa Reach:
SEMrush Rank (US): (View worldwide rankings)
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Alexa Graphs

Rank (12 Month Period)
Alexa Rank Graph for mycima.tube
Search (12 Month Period)
Alexa Search Graph for mycima.tube
Traffic

Visitors

Daily Visitors (Unique): 262,538
Monthly Visitors (Unique): 7,990,830
Yearly Visitors (Unique): 95,826,370
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1,647 USD
Monthly Revenue: $50,142 USD
Yearly Revenue: $601,303 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: mycima.tube 11
Domain Name: mycima 6
Extension (TLD): tube 4
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 75
Performance 91
Accessibility 85
Best Practices 83
SEO 92
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://mycima.tube/
Updated: 17th June, 2022

1.45 seconds
First Contentful Paint (FCP)
81%
9%
10%

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

Simulate loading on desktop
91

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.8 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 — 10 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.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted.

Audits

Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mycima.tube/
http/1.1
0
63.227999955416
723
0
301
text/plain
https://mycima.tube/
h2
63.668000046164
692.75799999014
55060
362271
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-128370636-1
h2
714.88699992187
735.08500005119
40586
102855
200
application/javascript
Script
https://fonts.gstatic.com/s/bevan/v12/4iCj6KZ0a9NXjG8dWCs.woff2
h2
741.68600002304
745.93400000595
20911
19984
200
font/woff2
Font
https://fonts.gstatic.com/s/tajawal/v3/Iurf6YBj_oCad4k1l8KiHrRpiYlJ.woff2
h2
741.96799984202
745.19399995916
9413
8488
200
font/woff2
Font
https://fonts.gstatic.com/s/tajawal/v3/Iurf6YBj_oCad4k1l8KiHrFpiQ.woff2
h2
742.18699987978
746.33400002494
10790
9864
200
font/woff2
Font
https://fonts.gstatic.com/s/tajawal/v3/Iurf6YBj_oCad4k1l5anHrFpiQ.woff2
h2
742.69199999981
746.62899994291
11508
10580
200
font/woff2
Font
https://fonts.gstatic.com/s/tajawal/v3/Iurf6YBj_oCad4k1l5anHrRpiYlJ.woff2
h2
758.0719999969
762.42599985562
9874
8948
200
font/woff2
Font
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/jquery-3.4.1.min.js?ver=5.9.1
h2
788.07100001723
861.33600003086
32547
88059
200
application/javascript
Script
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/owl.carousel.min.js?ver=5.9.1
h2
788.60999993049
866.00299994461
23782
95124
200
application/javascript
Script
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/setup.js?971882650&ver=5.9.1
h2
788.72399986722
1096.0329999216
20732
138084
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
895.10799990967
902.6699999813
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=92358202&t=pageview&_s=1&dl=https%3A%2F%2Fmycima.tube%2F&ul=en-us&de=UTF-8&dt=%D9%85%D8%B4%D8%A7%D9%87%D8%AF%D8%A9%20%D9%85%D8%A7%D9%89%20%D8%B3%D9%8A%D9%85%D8%A7%20MYCIMA%20%D8%A7%D9%81%D9%84%D8%A7%D9%85%20%D9%88%20%D9%85%D8%B3%D9%84%D8%B3%D9%84%D8%A7%D8%AA%20%D8%A7%D9%88%D9%86%20%D9%84%D8%A7%D9%8A%D9%86%20-%20%D9%85%D8%A7%D9%8A%20%D8%B3%D9%8A%D9%85%D8%A7&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=214544973&gjid=1259690372&cid=952899089.1655440949&tid=UA-128370636-1&_gid=563588546.1655440949&_r=1&gtm=2ou6f0&z=148369239
h2
944.76699992083
949.48900002055
610
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j96&tid=UA-128370636-1&cid=952899089.1655440949&jid=214544973&gjid=1259690372&_gid=563588546.1655440949&_u=YEBAAUAAAAAAAC~&z=454950329
h2
952.61100004427
957.28199998848
683
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j96&tid=UA-128370636-1&cid=952899089.1655440949&jid=214544973&_u=YEBAAUAAAAAAAC~&z=246005949
h2
960.08099988103
969.29399995133
673
42
200
image/gif
Image
https://mycima.tube/insights.php
h2
1170.7349999342
1389.0859999228
726
34
200
application/json
XHR
https://mycima.tube/AjaxCenter/RightBar/
h2
1195.9160000551
1426.6089999583
11056
85008
200
text/html
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
736.342
9.669
754.726
19.842
774.581
33.353
828.781
81.468
910.313
10.645
923.025
11.567
935.349
14.819
961.81
22.941
1140.706
110.302
1251.037
22.449
1274.381
19.68
1294.526
22.626
1448.526
6.509
1467.267
12.766
1480.091
31.482
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Used for treemap app

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mycima.tube should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Mycima.tube should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mycima.tube should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 2 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mycima.tube should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
@font-face {font-family: 'Bevan';font-style: normal;font-weight: 400;font-display: swap; ... } ...
36048
2385
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mycima.tube should consider minifying JS files.
Reduce unused CSS — Potential savings of 32 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mycima.tube 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)
@font-face {font-family: 'Bevan';font-style: normal;font-weight: 400;font-display: swap; ... } ...
36048
32479
Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease 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
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
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.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Mycima.tube should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mycima.tube/
190
https://mycima.tube/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mycima.tube 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
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time.
Avoids enormous network payloads — Total size was 264 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://mycima.tube/
55060
https://www.googletagmanager.com/gtag/js?id=UA-128370636-1
40586
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/jquery-3.4.1.min.js?ver=5.9.1
32547
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/owl.carousel.min.js?ver=5.9.1
23782
https://fonts.gstatic.com/s/bevan/v12/4iCj6KZ0a9NXjG8dWCs.woff2
20911
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/setup.js?971882650&ver=5.9.1
20732
https://www.google-analytics.com/analytics.js
20631
https://fonts.gstatic.com/s/tajawal/v3/Iurf6YBj_oCad4k1l5anHrFpiQ.woff2
11508
https://mycima.tube/AjaxCenter/RightBar/
11056
https://fonts.gstatic.com/s/tajawal/v3/Iurf6YBj_oCad4k1l8KiHrFpiQ.woff2
10790
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mycima.tube should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://mycima.tube/
286.537
4.246
1.983
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/setup.js?971882650&ver=5.9.1
96.237
63.263
2.35
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/jquery-3.4.1.min.js?ver=5.9.1
68.093
33.179
1.353
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)
Style & Layout
169.112
Script Evaluation
150.578
Other
112.899
Rendering
62.751
Parse HTML & CSS
38.853
Script Parsing & Compilation
10.358
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 — 17 requests • 264 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
17
270305
Script
5
138278
Font
5
62496
Document
1
55060
Other
5
13798
Image
1
673
Stylesheet
0
0
Media
0
0
Third-party
10
125679
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)
62496
0
40586
0
21241
0
683
0
673
0
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required.
Largest Contentful Paint element — 1 element found
This is the largest contentful element painted within the viewport. Learn More
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 — 5 elements found
These DOM elements contribute most to the CLS of the page.
Element CLS Contribution
0.21126871552403
0.056146572104019
0.0009793420190796
0.00091996727645944
0.0004896710095398
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
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay.
URL Start Time (Ms) Duration (Ms)
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/setup.js?971882650&ver=5.9.1
753
55
Image elements have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve 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 mycima.tube on mobile screens.
Avoids `unload` event listeners
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events 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
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly.

Other

Serve static assets with an efficient cache policy — 4 resources found
Mycima.tube can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20631
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/jquery-3.4.1.min.js?ver=5.9.1
14400000
32547
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/owl.carousel.min.js?ver=5.9.1
14400000
23782
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/setup.js?971882650&ver=5.9.1
14400000
20732

Metrics

Cumulative Layout Shift — 0.27
Cumulative Layout Shift measures the movement of visible elements within the viewport.
View Data

Other

Reduce initial server response time — Root document took 630 ms
Keep the server response time for the main document short because all other requests depend on it.
URL Time Spent (Ms)
https://mycima.tube/
630.079
Avoid an excessive DOM size — 2,878 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
2878
Maximum DOM Depth
19
Maximum Child Elements
282
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
85

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mycima.tube. 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
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies.
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
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document ``.
`[aria-hidden="true"]` elements do not contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers.
ARIA `meter` elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers.
ARIA `progressbar` elements have accessible names
When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for 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
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers.
ARIA `tooltip` elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers.
ARIA `treeitem` elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for 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
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies.

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.

Names and labels

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
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels.
`<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.
`<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.

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"]`
Mycima.tube may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not 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.
Failing Elements
Links do not 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.

Contrast

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that mycima.tube 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
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks.
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
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity.
Fonts with `font-display: optional` are preloaded
Preload `optional` fonts so first-time visitors may use them.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.4.1
WordPress
5.9.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits.
No issues in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

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

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More

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 mycima.tube. 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 mycima.tube 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
A maskable icon ensures that the image fills the entire shape without being letterboxed 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 82
Accessibility 96
Best Practices 83
SEO 93
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://mycima.tube/
Updated: 17th June, 2022

1.40 seconds
First Contentful Paint (FCP)
84%
9%
7%

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

Simulate loading on mobile
82

Performance

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

Metrics

Speed Index — 2.5 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 190 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 — 2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mycima.tube should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Mycima.tube should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mycima.tube should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 2 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mycima.tube should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
@font-face {font-family: 'Bevan';font-style: normal;font-weight: 400;font-display: swap; ... } ...
36273
2400
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mycima.tube should consider minifying JS files.
Reduce unused CSS — Potential savings of 33 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mycima.tube 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)
@font-face {font-family: 'Bevan';font-style: normal;font-weight: 400;font-display: swap; ... } ...
36273
34257
Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease 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
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
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 320 ms
Keep the server response time for the main document short because all other requests depend on it.
URL Time Spent (Ms)
https://mycima.tube/
322.058
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Mycima.tube should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mycima.tube/
630
https://mycima.tube/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mycima.tube 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
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time.
Avoids enormous network payloads — Total size was 264 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://mycima.tube/
55404
https://www.googletagmanager.com/gtag/js?id=UA-128370636-1
40586
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/jquery-3.4.1.min.js?ver=5.9.1
32541
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/owl.carousel.min.js?ver=5.9.1
23780
https://fonts.gstatic.com/s/bevan/v12/4iCj6KZ0a9NXjG8dWCs.woff2
20899
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/setup.js?971882650&ver=5.9.1
20732
https://www.google-analytics.com/analytics.js
20631
https://fonts.gstatic.com/s/tajawal/v3/Iurf6YBj_oCad4k1l5anHrFpiQ.woff2
11495
https://mycima.tube/AjaxCenter/RightBar/
11054
https://fonts.gstatic.com/s/tajawal/v3/Iurf6YBj_oCad4k1l8KiHrFpiQ.woff2
10790
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mycima.tube 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.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://mycima.tube/
788.988
10.76
5.248
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/setup.js?971882650&ver=5.9.1
355.448
208.748
8.216
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/jquery-3.4.1.min.js?ver=5.9.1
346.636
145.632
6.66
Unattributable
124.924
9.968
0.612
https://www.google-analytics.com/analytics.js
86.288
67.448
3.536
https://www.googletagmanager.com/gtag/js?id=UA-128370636-1
81.912
73.056
6.58
Minimizes main-thread work — 1.8 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)
Style & Layout
602.72
Script Evaluation
521.668
Other
360.016
Rendering
156.352
Parse HTML & CSS
120.968
Script Parsing & Compilation
36.672
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 — 17 requests • 264 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
17
270599
Script
5
138270
Font
5
62472
Document
1
55404
Other
5
13780
Image
1
673
Stylesheet
0
0
Media
0
0
Third-party
10
125655
Minimize third-party usage — Third-party code blocked the main thread for 10 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)
21241
7.248
62472
0
40586
0
683
0
673
0
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required.
Largest Contentful Paint element — 1 element found
This is the largest contentful element painted within the viewport. Learn More
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.
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
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay.
URL Start Time (Ms) Duration (Ms)
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/setup.js?971882650&ver=5.9.1
2910
224
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/jquery-3.4.1.min.js?ver=5.9.1
2010
65
https://www.google-analytics.com/analytics.js
3796
65
https://mycima.tube/
1559
63
https://mycima.tube/
1410
53
https://mycima.tube/
1507
52
Avoid non-composited animations — 38 animated elements found
Animations which are not composited can be janky and increase CLS.
Element Name
Image elements have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve 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 mycima.tube on mobile screens.
Avoids `unload` event listeners
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events 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
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mycima.tube/
http/1.1
0
24.874000111595
703
0
301
text/plain
https://mycima.tube/
h2
25.237000081688
346.30300011486
55404
362271
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-128370636-1
h2
362.31300001964
380.34700020216
40586
102855
200
application/javascript
Script
https://fonts.gstatic.com/s/bevan/v12/4iCj6KZ0a9NXjG8dWCs.woff2
h2
380.04299998283
540.28500011191
20899
19984
200
font/woff2
Font
https://fonts.gstatic.com/s/tajawal/v3/Iurf6YBj_oCad4k1l8KiHrRpiYlJ.woff2
h2
380.78100001439
384.2949999962
9414
8488
200
font/woff2
Font
https://fonts.gstatic.com/s/tajawal/v3/Iurf6YBj_oCad4k1l8KiHrFpiQ.woff2
h2
380.9440000914
384.60300001316
10790
9864
200
font/woff2
Font
https://fonts.gstatic.com/s/tajawal/v3/Iurf6YBj_oCad4k1l5anHrFpiQ.woff2
h2
381.03600009345
419.13500009105
11495
10580
200
font/woff2
Font
https://fonts.gstatic.com/s/tajawal/v3/Iurf6YBj_oCad4k1l5anHrRpiYlJ.woff2
h2
392.28600007482
395.54599998519
9874
8948
200
font/woff2
Font
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/jquery-3.4.1.min.js?ver=5.9.1
h2
413.48400013521
448.60000000335
32541
88059
200
application/javascript
Script
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/owl.carousel.min.js?ver=5.9.1
h2
413.62000000663
473.63500017673
23780
95124
200
application/javascript
Script
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/setup.js?971882650&ver=5.9.1
h2
415.07000010461
683.73000016436
20732
138084
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
494.54700015485
500.82000019029
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=1481701442&t=pageview&_s=1&dl=https%3A%2F%2Fmycima.tube%2F&ul=en-us&de=UTF-8&dt=%D9%85%D8%B4%D8%A7%D9%87%D8%AF%D8%A9%20%D9%85%D8%A7%D9%89%20%D8%B3%D9%8A%D9%85%D8%A7%20MYCIMA%20%D8%A7%D9%81%D9%84%D8%A7%D9%85%20%D9%88%20%D9%85%D8%B3%D9%84%D8%B3%D9%84%D8%A7%D8%AA%20%D8%A7%D9%88%D9%86%20%D9%84%D8%A7%D9%8A%D9%86%20-%20%D9%85%D8%A7%D9%8A%20%D8%B3%D9%8A%D9%85%D8%A7&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=1678294796&gjid=698587436&cid=1202236009.1655440971&tid=UA-128370636-1&_gid=1052476343.1655440971&_r=1&gtm=2ou6f0&z=577423480
h2
534.67000019737
538.47200004384
610
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j96&tid=UA-128370636-1&cid=1202236009.1655440971&jid=1678294796&gjid=698587436&_gid=1052476343.1655440971&_u=YEBAAUAAAAAAAC~&z=680184266
h2
540.81500018947
544.27900002338
683
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j96&tid=UA-128370636-1&cid=1202236009.1655440971&jid=1678294796&_u=YEBAAUAAAAAAAC~&z=1958805483
h2
548.71000000276
557.01400013641
673
42
200
image/gif
Image
https://mycima.tube/insights.php
h2
739.49000006542
952.30700005777
730
34
200
application/json
XHR
https://mycima.tube/AjaxCenter/RightBar/
h2
775.67300014198
1011.6820000112
11054
85008
200
text/html
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
396.537
6.37
410.184
13.157
423.349
22.045
461.89
26.018
489.265
10.009
501.823
31.467
533.312
8.903
542.548
16.194
566.251
16.272
735.751
111.945
847.716
11.561
859.933
24.668
885.077
23.06
1060.292
10.69
1367.054
5.764
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Used for treemap app

Metrics

First Contentful Paint — 2.3 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 3.9 s
The time taken for the page to become fully interactive.

Audits

Max Potential First Input Delay — 220 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.3 s
The time taken for the primary content of the page to be rendered.

Other

Serve static assets with an efficient cache policy — 4 resources found
Mycima.tube can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20631
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/jquery-3.4.1.min.js?ver=5.9.1
14400000
32541
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/owl.carousel.min.js?ver=5.9.1
14400000
23780
https://mycima.tube/wp-content/themes/Mycima2021/components/packs/%23footer/js/setup.js?971882650&ver=5.9.1
14400000
20732

Metrics

Cumulative Layout Shift — 0.319
Cumulative Layout Shift measures the movement of visible elements within the viewport.
View Data

Other

Avoid an excessive DOM size — 2,885 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
2885
Maximum DOM Depth
19
Maximum Child Elements
282
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
First Contentful Paint (3G) — 4590 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
96

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mycima.tube. 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
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies.
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
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document ``.
`[aria-hidden="true"]` elements do not contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers.
ARIA `meter` elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers.
ARIA `progressbar` elements have accessible names
When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for 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
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers.
ARIA `tooltip` elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers.
ARIA `treeitem` elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for 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
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies.

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
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels.
`<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"]`
Mycima.tube 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

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that mycima.tube 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
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks.
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
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity.
Fonts with `font-display: optional` are preloaded
Preload `optional` fonts so first-time visitors may use them.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.4.1
WordPress
5.9.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits.
No issues in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

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

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More

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 mycima.tube. 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 mycima.tube 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
A maskable icon ensures that the image fills the entire shape without being letterboxed 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: 104.21.86.108
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: Yes
Name: REDACTED FOR PRIVACY
Organization: eng
Country: EG
City: REDACTED FOR PRIVACY
State: semoha
Post Code: REDACTED FOR PRIVACY
Email:
Phone: REDACTED FOR PRIVACY
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Name.com, Inc. 107.162.140.96
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 17th November, 2021
Valid To: 16th November, 2022
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: 3102913245918868740076508238262407795
Serial Number (Hex): 0255996F3B6212C026805C10AD959273
Valid From: 17th November, 2022
Valid To: 16th November, 2022
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 : 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 : Nov 17 00:34:11.822 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:55:45:7D:9D:09:8F:6B:E2:FA:6A:01:A3:
C4:81:DA:EE:C4:2F:AD:C3:8A:DC:01:40:ED:9A:E1:36:
05:46:4D:C2:02:20:15:37:A5:35:08:A5:61:DA:F8:7A:
01:8F:0A:94:84:26:04:D6:EB:54:11:40:2B:9D:39:DD:
C0:50:F5:B6:88:DC
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 : Nov 17 00:34:11.901 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:F0:1A:89:7A:D3:8A:74:97:2E:01:FF:
83:23:50:C7:1D:0F:44:65:3A:EA:44:6B:8C:F7:57:87:
85:01:4F:AA:81:02:20:09:BD:72:E3:23:7B:8F:8A:25:
B3:60:1A:90:8A:EB:9D:A6:CD:69:C8:49:92:01:C9:6A:
43:91:21:34:F8:16:8F
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Nov 17 00:34:11.814 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:2C:9B:95:36:61:AD:1B:6F:50:D9:CC:99:
7B:64:92:72:30:DC:68:24:FC:C3:86:22:A3:3A:D3:58:
76:1C:A4:E0:02:20:71:0E:9F:BD:F2:03:A8:A3:BA:94:
01:55:FA:0F:E1:19:30:B1:1D:6A:BF:D3:1E:90:57:B3:
A6:EF:45:1D:F9:99
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:mycima.tube
DNS:sni.cloudflaressl.com
DNS:*.mycima.tube
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 21st June, 2022
Content-Type: text/html; charset=utf-8
Server: cloudflare
Connection: keep-alive
Last-Modified: 21st June, 2022
Access-Control-Allow-Origin: *
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=BVi95TPHoswHJn1CDWQ92xE7APyHOSsJKOgDQIHZsulr5%2BPWlgqOmDgabVCzQp%2F0EGHjNTymWEVlZxc1xZ0XpPAhLCm1wVKSo0tFYSHhGtSXPD3srTWWPP5k4FNr%2BQ%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 71ecfd4a78781a0f-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 18th December, 2020
Changed: 29th December, 2021
Expires: 18th December, 2022
Registrar: Name.com, Inc.
Status: clientTransferProhibited
Nameservers: chad.ns.cloudflare.com
jean.ns.cloudflare.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: eng
Owner Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: semoha
Owner Country: EG
Owner Phone: REDACTED FOR PRIVACY
Owner Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

Nameservers

Name IP Address
chad.ns.cloudflare.com 173.245.59.82
jean.ns.cloudflare.com 173.245.58.121
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$2,477 USD 2/5