mobiletvshows.com

mobiletvshows.com is SSL secured

Free website and domain report on mobiletvshows.com

Last Updated: 11th July, 2023 Update Now
Overview

Snoop Summary for mobiletvshows.com

This is a free and comprehensive report about mobiletvshows.com. The domain mobiletvshows.com is currently hosted on a server located in United States with the IP address 199.59.243.200, where the local currency is USD and English is the local language. If mobiletvshows.com was to be sold it would possibly be worth $380 USD (based on the daily revenue potential of the website over a 24 month period). Mobiletvshows.com is somewhat popular with an estimated 178 daily unique visitors. This report was last updated 11th July, 2023.

About mobiletvshows.com

Site Preview: mobiletvshows.com mobiletvshows.com
Title:
Description: See related links to what you are looking for.
Keywords and Tags: business
Related Terms:
Fav Icon:
Age: Over 11 years old
Domain Created: 1st August, 2012
Domain Updated: 22nd February, 2019
Domain Expires: 1st August, 2024
Review

Snoop Score

1/5

Valuation

$380 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 6,821,686
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 1
Moz Page Authority: 1

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 178
Monthly Visitors: 5,418
Yearly Visitors: 64,970
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $15 USD
Yearly Revenue: $185 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: mobiletvshows.com 17
Domain Name: mobiletvshows 13
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 74
Performance 98
Accessibility 76
Best Practices 80
SEO 100
Progressive Web App 18
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
98

Performance

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

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
Total Blocking Time — 20 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

Other

Max Potential First Input Delay — 100 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 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://mobiletvshows.com/
http/1.1
0
76.420000055805
4502
4089
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
88.70000008028
103.04800001904
61325
171835
200
text/javascript
Script
http://mobiletvshows.com/px.gif?ch=1&rn=8.230150392268664
http/1.1
89.69400008209
165.35000002477
275
42
200
image/gif
Image
http://mobiletvshows.com/px.gif?ch=2&rn=8.230150392268664
http/1.1
90.18699999433
146.91100001801
275
42
200
image/gif
Image
http://mobiletvshows.com/glp?r=&u=http%3A%2F%2Fmobiletvshows.com%2F&rw=800&rh=600&ww=1350&wh=940
http/1.1
190.33200002741
273.73500005342
11156
10812
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Open+Sans
h2
276.94800007157
288.46700000577
1276
2085
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Quicksand
h2
277.92000002228
292.34300006647
1172
1090
200
text/css
Stylesheet
http://mobiletvshows.com/public/legacy/10355/resources/arrows-bg.jpg
http/1.1
285.05900001619
398.10900005978
96086
95846
200
image/jpeg
Image
http://mobiletvshows.com/public/legacy/10355/resources/arrows-bg-ext.png
http/1.1
285.2379999822
358.89000003226
1379
1143
200
image/png
Image
https://www.google.com/dp/ads?adsafe=low&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol119&cpp=0&hl=en&client=dp-bodis30_3ph&r=m&type=3&max_radlink_len=60&swp=as-drid-2776760838494698&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300494%2C17300496&format=r7&num=0&output=afd_ads&domain_name=mobiletvshows.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1622834751660&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=932&frm=0&uio=ff6fa6sa11st24lt30sl1sr1-&cont=Sb&csize=w400h0&inames=master-1&jsv=21803&rurl=http%3A%2F%2Fmobiletvshows.com%2F
h2
295.86000007112
416.65000002831
8198
10716
200
text/html
Document
http://www.google-analytics.com/analytics.js
http/1.1
297.53500001971
301.80200003088
20025
49153
200
text/javascript
Script
http://ads.pro-market.net/ads/scripts/site-110930.js
http/1.1
297.95500007458
394.47000005748
1085
1404
200
application/x-javascript
Script
https://fonts.gstatic.com/s/quicksand/v22/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xDwxUD2GFw.woff
h2
303.75600000843
306.30500009283
17659
17096
200
font/woff
Font
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=435134264&t=pageview&_s=1&dl=http%3A%2F%2Fmobiletvshows.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=Mobiletvshows.com&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAAC~&jid=1728742775&gjid=1412871253&cid=1250521220.1622834752&tid=UA-12311409-3&_gid=1328155854.1622834752&_r=1&_slc=1&z=322899596
h2
334.29600007366
338.17800006364
620
2
200
text/plain
XHR
https://pbid.pro-market.net/engine?site=110930;size=1x1;e=0;category=nw2a2ec319nwt%203g3;kw=nw2a2ec319nwt%203g3;rnd=(1622834751780)
h2
406.75500000361
446.8910000287
951
429
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
537.05200005788
552.29200003669
61380
171853
200
text/javascript
Script
https://ads.pro-market.net/ads/scripts/dda4-1-8.js
http/1.1
538.99600007571
742.18000005931
8841
29303
200
application/x-javascript
Script
https://fonts.googleapis.com/css?family=open%20sans%7Copen%20sans
579.89400008228
596.26000002027
0
0
-1
Stylesheet
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6Im1vYmlsZXR2c2hvd3MuY29tIiwic2VydmVyIjoxNjEsInRlcm1zIjpbXSwiVVJMIjoiaHR0cDpcL1wvbW9iaWxldHZzaG93cy5jb21cLyIsInJlZmVycmVyIjoiIiwiZHciOjEzNTAsImRoIjo5NDAsInJ3Ijo4MDAsInJoIjo2MDB9&t=1622834751&abp=0
http/1.1
585.81299998332
650.73700004723
356
0
200
text/plain
XHR
https://www.google.com/js/bg/Jl_KA3DWLl1pqAl7nrDeic27IkrJD7_aVFtTlraQVeY.js
h2
608.81000000518
612.73799999617
6352
14652
200
text/javascript
Script
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=iw1t4xm8dgk6&aqid=P366YLOALfqNoPwPiMKM0Ac&pbt=bs&adbx=475&adby=167&adbh=365&adbw=400&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=2180385865384987480&csadii=12&csadr=302&lle=0&llm=1000&ifv=1&usr=0
h2
2097.2110000439
2137.3240000103
461
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=stdmlkrrx0j2&aqid=P366YLOALfqNoPwPiMKM0Ac&pbt=bv&adbx=475&adby=167&adbh=365&adbw=400&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=2180385865384987480&csadii=12&csadr=302&lle=0&llm=1000&ifv=1&usr=0
h2
2597.8170000017
2636.1380000599
461
0
204
text/html
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)
86.263
6.435
122.703
8.049
281.709
23.494
315.535
26.171
402.459
9.128
425.318
60.491
485.821
6.423
492.257
7.158
499.515
41.891
569.577
21.454
592.745
5.812
603.842
9.132
620.797
95.795
750.219
6.121
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.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mobiletvshows.com 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. Mobiletvshows.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mobiletvshows.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mobiletvshows.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mobiletvshows.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mobiletvshows.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 53 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://mobiletvshows.com/public/legacy/10355/resources/arrows-bg.jpg
95846
54366
Enable text compression — Potential savings of 8 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://mobiletvshows.com/glp?r=&u=http%3A%2F%2Fmobiletvshows.com%2F&rw=800&rh=600&ww=1350&wh=940
10812
6231
http://mobiletvshows.com/
4089
2253
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 80 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)
http://mobiletvshows.com/
77.417
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Mobiletvshows.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mobiletvshows.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 20 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)
http://mobiletvshows.com/glp?r=&u=http%3A%2F%2Fmobiletvshows.com%2F&rw=800&rh=600&ww=1350&wh=940
20161
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 297 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://mobiletvshows.com/public/legacy/10355/resources/arrows-bg.jpg
96086
https://www.google.com/adsense/domains/caf.js
61380
http://www.google.com/adsense/domains/caf.js
61325
http://www.google-analytics.com/analytics.js
20025
https://fonts.gstatic.com/s/quicksand/v22/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xDwxUD2GFw.woff
17659
http://mobiletvshows.com/glp?r=&u=http%3A%2F%2Fmobiletvshows.com%2F&rw=800&rh=600&ww=1350&wh=940
11156
https://ads.pro-market.net/ads/scripts/dda4-1-8.js
8841
https://www.google.com/dp/ads?adsafe=low&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol119&cpp=0&hl=en&client=dp-bodis30_3ph&r=m&type=3&max_radlink_len=60&swp=as-drid-2776760838494698&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300494%2C17300496&format=r7&num=0&output=afd_ads&domain_name=mobiletvshows.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1622834751660&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=932&frm=0&uio=ff6fa6sa11st24lt30sl1sr1-&cont=Sb&csize=w400h0&inames=master-1&jsv=21803&rurl=http%3A%2F%2Fmobiletvshows.com%2F
8198
https://www.google.com/js/bg/Jl_KA3DWLl1pqAl7nrDeic27IkrJD7_aVFtTlraQVeY.js
6352
http://mobiletvshows.com/
4502
Avoids an excessive DOM size — 19 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
19
Maximum DOM Depth
7
Maximum Child Elements
8
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mobiletvshows.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js
127.706
117.607
5.858
http://mobiletvshows.com/
125.086
5.937
1.409
Minimizes main-thread work — 0.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
193.089
Rendering
107.299
Other
46.899
Script Parsing & Compilation
19.994
Style & Layout
17.849
Parse HTML & CSS
4.473
Garbage Collection
3.715
Keep request counts low and transfer sizes small — 22 requests • 297 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
303835
Script
7
170164
Image
6
98937
Font
1
17659
Document
3
13651
Stylesheet
3
2448
Other
2
976
Media
0
0
Third-party
16
190162
Minimize third-party usage — Third-party code blocked the main thread for 30 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)
138177
33.732
20645
0
20107
0
10877
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
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00021128841607565
0.00010884554767533
0.00010244286840032
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google.com/js/bg/Jl_KA3DWLl1pqAl7nrDeic27IkrJD7_aVFtTlraQVeY.js
813
96
http://mobiletvshows.com/
194
60
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.

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.

Opportunities

Reduce unused JavaScript — Potential savings of 74 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
61325
40482
https://www.google.com/adsense/domains/caf.js
61380
35684

Diagnostics

Serve static assets with an efficient cache policy — 6 resources found
Mobiletvshows.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://mobiletvshows.com/public/legacy/10355/resources/arrows-bg.jpg
0
96086
http://mobiletvshows.com/public/legacy/10355/resources/arrows-bg-ext.png
0
1379
http://mobiletvshows.com/px.gif?ch=1&rn=8.230150392268664
0
275
http://mobiletvshows.com/px.gif?ch=2&rn=8.230150392268664
0
275
http://www.google-analytics.com/analytics.js
7200000
20025
http://ads.pro-market.net/ads/scripts/site-110930.js
86400000
1085

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/quicksand/v22/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xDwxUD2GFw.woff
2.5490000844002
Avoid `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.
Source
76

Accessibility

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

Navigation

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

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
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 `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

Contrast

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

Internationalization and localization

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

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
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

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.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 10 insecure requests 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://mobiletvshows.com/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://mobiletvshows.com/px.gif?ch=1&rn=8.230150392268664
Allowed
http://mobiletvshows.com/px.gif?ch=2&rn=8.230150392268664
Allowed
http://mobiletvshows.com/glp?r=&u=http%3A%2F%2Fmobiletvshows.com%2F&rw=800&rh=600&ww=1350&wh=940
Allowed
http://mobiletvshows.com/public/legacy/10355/resources/arrows-bg.jpg
Allowed
http://mobiletvshows.com/public/legacy/10355/resources/arrows-bg-ext.png
Allowed
http://www.google-analytics.com/analytics.js
Allowed
http://ads.pro-market.net/ads/scripts/site-110930.js
Allowed
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6Im1vYmlsZXR2c2hvd3MuY29tIiwic2VydmVyIjoxNjEsInRlcm1zIjpbXSwiVVJMIjoiaHR0cDpcL1wvbW9iaWxldHZzaG93cy5jb21cLyIsInJlZmVycmVyIjoiIiwiZHciOjEzNTAsImRoIjo5NDAsInJ3Ijo4MDAsInJoIjo2MDB9&t=1622834751&abp=0
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Refused to apply style from 'https://fonts.googleapis.com/css?family=open%20sans%7Copen%20sans' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Refused to apply style from 'https://fonts.googleapis.com/css?family=open%20sans%7Copen%20sans' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
100

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mobiletvshows.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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.
18

Progressive Web App

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mobiletvshows.com on mobile screens.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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) 75
Performance 88
Accessibility 76
Best Practices 87
SEO 100
Progressive Web App 25
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
88

Performance

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

Metrics

First Contentful Paint — 1.1 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.9 s
The timing of the largest text or image that is painted.

Other

First Meaningful Paint — 1.3 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://mobiletvshows.com/
http/1.1
0
23.170000000391
4509
4089
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
35.38899999694
50.004999997327
61325
171835
200
text/javascript
Script
http://mobiletvshows.com/px.gif?ch=1&rn=9.211492385664664
http/1.1
37.022000004072
59.03400000534
275
42
200
image/gif
Image
http://mobiletvshows.com/px.gif?ch=2&rn=9.211492385664664
http/1.1
37.482000014279
107.45800001314
275
42
200
image/gif
Image
http://mobiletvshows.com/glp?r=&u=http%3A%2F%2Fmobiletvshows.com%2F&rw=360&rh=640&ww=360&wh=640
http/1.1
137.65600000625
179.84699999215
9784
9440
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Quicksand
h2
184.03900001431
194.57699998748
1170
1089
200
text/css
Stylesheet
https://www.google.com/dp/ads?adsafe=low&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol119&cpp=0&hl=en&client=dp-bodis30_3ph&r=m&type=3&max_radlink_len=60&swp=as-drid-2776760838494698&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300494%2C17300496&format=r5&num=0&output=afd_ads&domain_name=mobiletvshows.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1622834763912&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=132&frm=0&uio=ff6fa6sa11st24lt48sl1sr1-&cont=Sb&csize=w360h0&inames=master-1&jsv=21803&rurl=http%3A%2F%2Fmobiletvshows.com%2F
h2
206.2380000134
304.03200001456
8193
10443
200
text/html
Document
http://www.google-analytics.com/analytics.js
http/1.1
208.84100001422
213.84199999738
20026
49153
200
text/javascript
Script
http://ads.pro-market.net/ads/scripts/site-110930.js
http/1.1
209.29999998771
308.62399999751
1085
1404
200
application/x-javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=1890924024&t=pageview&_s=1&dl=http%3A%2F%2Fmobiletvshows.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=Mobiletvshows.com&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAAC~&jid=1219899498&gjid=1036978699&cid=31138962.1622834764&tid=UA-12311409-3&_gid=233903009.1622834764&_r=1&_slc=1&z=1259321742
h2
241.81500001578
245.5009999976
620
2
200
text/plain
XHR
https://pbid.pro-market.net/engine?site=110930;size=1x1;e=0;category=nw2a2ec319nwt%203g3;kw=nw2a2ec319nwt%203g3;rnd=(1622834764047)
h2
329.70199998817
369.31400001049
951
429
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
329.36199998949
350.97299999325
61380
171826
200
text/javascript
Script
https://afs.googleusercontent.com/dp-bodis/arrow-blue-2.png
h2
387.65799999237
391.31599999382
804
260
200
image/png
Image
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6Im1vYmlsZXR2c2hvd3MuY29tIiwic2VydmVyIjoxNjEsInRlcm1zIjpbXSwiVVJMIjoiaHR0cDpcL1wvbW9iaWxldHZzaG93cy5jb21cLyIsInJlZmVycmVyIjoiIiwiZHciOjM2MCwiZGgiOjY0MCwicnciOjM2MCwicmgiOjY0MH0&t=1622834763&abp=0
http/1.1
396.15700001013
444.29099999252
356
0
200
text/plain
XHR
https://www.google.com/js/bg/Jl_KA3DWLl1pqAl7nrDeic27IkrJD7_aVFtTlraQVeY.js
h2
418.93099999288
422.3570000031
6480
14652
200
text/javascript
Script
https://ads.pro-market.net/ads/scripts/dda4-1-8.js
http/1.1
419.92799998843
895.97700000741
8841
29303
200
application/x-javascript
Script
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=qx983diti4b5&aqid=S366YIfLO4rozwWUhKgo&pbt=bs&adbx=0&adby=50&adbh=413&adbw=360&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=2180385865384987480&csadii=16&csadr=212&lle=0&llm=1000&ifv=1&usr=0
h2
1917.3449999944
1954.0170000109
461
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=u4pbdflf1k0&aqid=S366YIfLO4rozwWUhKgo&pbt=bv&adbx=0&adby=50&adbh=413&adbw=360&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=2180385865384987480&csadii=16&csadr=212&lle=0&llm=1000&ifv=1&usr=0
h2
2417.9550000117
2451.3159999915
461
0
204
text/html
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)
32.631
6.527
67.637
9.603
187.883
28.424
225.42
23.749
314.471
6.634
323.488
10.514
368.857
25.75
395.195
6.321
407.86
11.437
430.318
99.939
904.093
6.802
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.
First Contentful Paint (3G) — 2169 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mobiletvshows.com 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. Mobiletvshows.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mobiletvshows.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mobiletvshows.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mobiletvshows.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mobiletvshows.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
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 — Potential savings of 7 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://mobiletvshows.com/glp?r=&u=http%3A%2F%2Fmobiletvshows.com%2F&rw=360&rh=640&ww=360&wh=640
9440
5225
http://mobiletvshows.com/
4089
2255
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 20 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)
http://mobiletvshows.com/
24.168
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Mobiletvshows.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mobiletvshows.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 20 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)
http://mobiletvshows.com/glp?r=&u=http%3A%2F%2Fmobiletvshows.com%2F&rw=360&rh=640&ww=360&wh=640
20251
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 183 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
61380
http://www.google.com/adsense/domains/caf.js
61325
http://www.google-analytics.com/analytics.js
20026
http://mobiletvshows.com/glp?r=&u=http%3A%2F%2Fmobiletvshows.com%2F&rw=360&rh=640&ww=360&wh=640
9784
https://ads.pro-market.net/ads/scripts/dda4-1-8.js
8841
https://www.google.com/dp/ads?adsafe=low&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol119&cpp=0&hl=en&client=dp-bodis30_3ph&r=m&type=3&max_radlink_len=60&swp=as-drid-2776760838494698&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300494%2C17300496&format=r5&num=0&output=afd_ads&domain_name=mobiletvshows.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1622834763912&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=132&frm=0&uio=ff6fa6sa11st24lt48sl1sr1-&cont=Sb&csize=w360h0&inames=master-1&jsv=21803&rurl=http%3A%2F%2Fmobiletvshows.com%2F
8193
https://www.google.com/js/bg/Jl_KA3DWLl1pqAl7nrDeic27IkrJD7_aVFtTlraQVeY.js
6480
http://mobiletvshows.com/
4509
https://fonts.googleapis.com/css?family=Quicksand
1170
http://ads.pro-market.net/ads/scripts/site-110930.js
1085
Uses efficient cache policy on static assets — 5 resources found
Mobiletvshows.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://mobiletvshows.com/px.gif?ch=1&rn=9.211492385664664
0
275
http://mobiletvshows.com/px.gif?ch=2&rn=9.211492385664664
0
275
http://www.google-analytics.com/analytics.js
7200000
20026
https://afs.googleusercontent.com/dp-bodis/arrow-blue-2.png
82800000
804
http://ads.pro-market.net/ads/scripts/site-110930.js
86400000
1085
Avoids an excessive DOM size — 21 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
21
Maximum DOM Depth
6
Maximum Child Elements
8
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mobiletvshows.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.8 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.google.com/adsense/domains/caf.js
566.028
505.492
22.812
http://mobiletvshows.com/glp?r=&u=http%3A%2F%2Fmobiletvshows.com%2F&rw=360&rh=640&ww=360&wh=640
115.012
72.74
4.26
http://www.google-analytics.com/analytics.js
100.356
90.004
4.852
Unattributable
86.732
10.592
0.62
http://mobiletvshows.com/
80.66
24.528
5.236
http://www.google.com/adsense/domains/caf.js
57.788
33.22
16.084
Minimizes main-thread work — 1.2 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
813.6
Other
175.372
Script Parsing & Compilation
82.716
Style & Layout
60.656
Rendering
20.652
Parse HTML & CSS
18.616
Garbage Collection
14.456
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 — 18 requests • 183 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
18
186996
Script
7
168921
Document
3
13653
Image
5
2276
Stylesheet
1
1170
Other
2
976
Media
0
0
Font
0
0
Third-party
14
172153
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
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.1068798828125
0.0584814453125
5.6016710069444E-6
Avoid long main-thread tasks — 4 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google.com/js/bg/Jl_KA3DWLl1pqAl7nrDeic27IkrJD7_aVFtTlraQVeY.js
3979
400
https://www.google.com/adsense/domains/caf.js
3548
103
http://www.google-analytics.com/analytics.js
2855
95
http://mobiletvshows.com/glp?r=&u=http%3A%2F%2Fmobiletvshows.com%2F&rw=360&rh=640&ww=360&wh=640
1868
57
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.

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 — 4.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 280 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.165
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

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

Opportunities

Reduce unused JavaScript — Potential savings of 74 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
61325
40522
https://www.google.com/adsense/domains/caf.js
61380
35629

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 350 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)
138300
313.748
20646
36.888
10877
0
1170
0
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
Avoid `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.
Source
76

Accessibility

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

Navigation

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

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
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 `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

Contrast

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

Internationalization and localization

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

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
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

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.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 8 insecure requests 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://mobiletvshows.com/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://mobiletvshows.com/px.gif?ch=1&rn=9.211492385664664
Allowed
http://mobiletvshows.com/px.gif?ch=2&rn=9.211492385664664
Allowed
http://mobiletvshows.com/glp?r=&u=http%3A%2F%2Fmobiletvshows.com%2F&rw=360&rh=640&ww=360&wh=640
Allowed
http://www.google-analytics.com/analytics.js
Allowed
http://ads.pro-market.net/ads/scripts/site-110930.js
Allowed
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6Im1vYmlsZXR2c2hvd3MuY29tIiwic2VydmVyIjoxNjEsInRlcm1zIjpbXSwiVVJMIjoiaHR0cDpcL1wvbW9iaWxldHZzaG93cy5jb21cLyIsInJlZmVycmVyIjoiIiwiZHciOjM2MCwiZGgiOjY0MCwicnciOjM2MCwicmgiOjY0MH0&t=1622834763&abp=0
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
100

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mobiletvshows.com on mobile screens.
Document uses legible font sizes — 95.45% 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
.amo
4.55%
11px
95.45%
≥ 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.
25

Progressive Web App

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mobiletvshows.com on mobile screens.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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: 199.59.243.200
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
Bodis, LLC
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.208.40.188
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: mobiletvshows.com
Issued By: R3
Valid From: 7th November, 2021
Valid To: 5th February, 2022
Subject: CN = mobiletvshows.com
Hash: aff92e3c
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03AE520E640B2C0806AAA84492DEA28CA190
Serial Number (Hex): 03AE520E640B2C0806AAA84492DEA28CA190
Valid From: 7th November, 2024
Valid To: 5th February, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 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 7 20:21:52.698 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:3B:36:0F:E2:D3:40:02:00:17:70:37:E6:
05:BB:70:42:B8:E8:C0:3C:C8:27:F7:A9:2A:BA:C2:AE:
25:D6:9D:AD:02:21:00:CF:30:0C:65:B0:EE:16:78:ED:
AA:14:87:66:E7:28:1D:B7:8D:32:46:46:3A:93:D1:9E:
4E:C6:9E:93:0C:22:CA
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 : Nov 7 20:21:52.851 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:1C:26:EE:EB:F7:ED:95:EA:E4:DF:F0:EA:
B5:12:9F:85:F5:48:EC:4D:32:92:97:F5:7B:E5:F3:2E:
68:4B:BB:DB:02:20:31:BE:2C:C7:13:8F:DB:2B:FB:9E:
D0:B7:82:0A:26:DE:07:14:5E:DC:84:D9:B1:87:E1:83:
1E:FE:B8:BB:78:C0
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:mobiletvshows.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
mobiletvshows.com. 199.59.243.200 IN 10800

NS Records

Host Nameserver Class TTL
mobiletvshows.com. ns1.bodis.com. IN 10800
mobiletvshows.com. ns2.bodis.com. IN 10800

SOA Records

Domain Name Primary NS Responsible Email TTL
mobiletvshows.com. ns1.bodis.com. dnsadmin.bodis.com. 10800

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: openresty
Date: 4th January, 2021
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBANDrp2lz7AOmADaN8tA50LsWcjLFyQFcb/P2Txc58oYOeILb3vBw7J6f4pamkAQVSQuqYsKx3YzdUHCvbVZvFUsCAwEAAQ==_nRAEJA4VBCYclFhSdlewDb3hVCs5iCMp56jcDjbkcMpL3ViFqhprtYKk9tQ78eVfbgXH/inMJUATM8eVgyOUtg==

Whois Lookup

Created: 1st August, 2012
Changed: 22nd February, 2019
Expires: 1st August, 2024
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns1.bodis.com
ns2.bodis.com
Owner State: yunnan province
Owner Country: CN
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=MOBILETVSHOWS.COM
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=MOBILETVSHOWS.COM
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=MOBILETVSHOWS.COM
Full Whois: Domain Name: MOBILETVSHOWS.COM
Registry Domain ID: 1736848371_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2019-02-22T08:09:47Z
Creation Date: 2012-08-01T18:01:45Z
Registrar Registration Expiration Date: 2024-08-01T18:01:45Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registrant Organization:
Registrant State/Province: yunnan province
Registrant Country: CN
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=MOBILETVSHOWS.COM
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=MOBILETVSHOWS.COM
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=MOBILETVSHOWS.COM
Name Server: NS1.BODIS.COM
Name Server: NS2.BODIS.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-01-10T04:32:42Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

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

Nameservers

Name IP Address
ns1.bodis.com 185.85.196.36
ns2.bodis.com 199.59.243.150
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$15,089 USD 3/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$114 USD 2/5
$291 USD 1/5
$921 USD 1/5
$7,412 USD 2/5
$10 USD 1/5