Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

dodear.com

dodear.com may not be SSL secured

Free website and domain report on dodear.com

Last Updated: 6th August, 2024 Update Now
Overview

Snoop Summary for dodear.com

This is a free and comprehensive report about dodear.com. Our records indicate that dodear.com is privately registered by Domains By Proxy, LLC. Dodear.com is expected to earn an estimated $238 USD per day from advertising revenue. The sale of dodear.com would possibly be worth $173,631 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Dodear.com receives an estimated 56,241 unique visitors every day - a massive amount of traffic! This report was last updated 6th August, 2024.

About dodear.com

Site Preview: dodear.com dodear.com
Title:
Description: Dodear.com is a complete internet entertainment portal including many sections such as online chat, forum, greetings, radio, islamic material, online games, movies and music information. Dodear.com provides quality and up-to-date material for their visitors.
Keywords and Tags: dodear, dodear home, dodear movies 2019 bollywood download, dodear net pk, dodear songs, dodear tv channel, dodear tv serial, internet services, popular, www do dare com, www dodear com portal entertainment, www dodear com video
Related Terms: dodear movies, dodear. com pk99507, material de curacion, material selection, pe material
Fav Icon:
Age: Over 17 years old
Domain Created: 18th January, 2007
Domain Updated: 17th September, 2019
Domain Expires: 18th January, 2028
Review

Snoop Score

3/5 (Great!)

Valuation

$173,631 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 19,392
Alexa Reach:
SEMrush Rank (US): 568,580
SEMrush Authority Score: 53
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 591 0
Traffic: 1,876 0
Cost: $2 USD $0 USD
Traffic

Visitors

Daily Visitors: 56,241
Monthly Visitors: 1,711,799
Yearly Visitors: 20,527,965
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $238 USD
Monthly Revenue: $7,239 USD
Yearly Revenue: $86,811 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 4,645
Referring Domains: 458
Referring IPs: 312
Dodear.com has 4,645 backlinks according to SEMrush. 43% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve dodear.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
98% of dodear.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://markosweb.com/www/dodear.com/
Target: https://dodear.com/
2
Source: http://www.lire.me/search/Dailymotion.com::%7C::Password/pdf/4
Target: http://www.dodear.com/
3
Source: http://avanimovies.blogspot.com/2019/11/captain-marvel-movie-in-hindi-download.html
Target: http://english.dodear.com/movies/english/c/CaptainMarvel.2019/CaptainMarvel.2019.BRRip.Dual.mkv
4
Source: https://popularmovie.my.id/jennifer-lopez-dance-again-2014.html
Target: http://videos.files.dodear.com/videos/2015/01/vJoVYwWteTZC/vJoVYwWteTZC.jpg
5
Source: http://popularmovies.my.id/redrum-2018-imdb.html
Target: http://files.dodear.com/movies/images/TNA.Impact.2018.12.13-15447700675621.jpg

Top Ranking Keywords (US)

1
Keyword: dodear
Ranked Page: http://www.dodear.com/en/webtv/21399
2
Keyword: dodear tv channel
Ranked Page: http://www.dodear.com/en/webtv
3
Keyword: dodear tv serial
Ranked Page: http://www.dodear.com/en/webtv
4
Keyword: dodear net pk
Ranked Page: http://www.dodear.com/en/movie
5
Keyword: www dodear com portal entertainment
Ranked Page: http://www.dodear.com/en/videos

Domain Analysis

Value Length
Domain: dodear.com 10
Domain Name: dodear 6
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.99 seconds
Load Time Comparison: Faster than 78% of sites

PageSpeed Insights

Avg. (All Categories) 83
Performance 95
Accessibility 83
Best Practices 73
SEO 82
Progressive Web App 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://www.dodear.com/en/home
Updated: 18th August, 2021

2.27 seconds
First Contentful Paint (FCP)
67%
18%
15%

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

Simulate loading on desktop
95

Performance

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

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 1.0 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 — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://dodear.com/
http/1.1
0
423.77500000293
350
0
301
text/html
http://www.dodear.com/
http/1.1
424.2320000194
843.78200001083
343
0
302
text/html
http://www.dodear.com/en/home
http/1.1
844.30300001986
1108.9320000028
5964
11406
200
text/html
Document
http://www.dodear.com/public/assets/bootstrap/css/bootstrap.min.css
http/1.1
1121.1400000029
1726.4960000175
20022
121200
200
text/css
Stylesheet
http://www.dodear.com/public/assets/font-awesome/css/font-awesome.min.css
http/1.1
1121.4519999921
1324.8540000059
7381
31000
200
text/css
Stylesheet
http://www.dodear.com/public/responsive/css/style.css
http/1.1
1121.5899999952
1725.8659999934
18633
110000
200
text/css
Stylesheet
http://www.dodear.com/public/thirdparty/circular_carousel/css/style.css
http/1.1
1121.8579999986
1538.9520000026
1475
3787
200
text/css
Stylesheet
http://www.dodear.com/public/responsive/css/skin-2.css
http/1.1
1122.0630000171
1527.4740000023
794
1047
200
text/css
Stylesheet
http://www.dodear.com/public/assets/jquery/jquery-3.2.1.min.js
http/1.1
1122.2830000042
1742.0310000016
30624
86659
200
application/javascript
Script
http://www.dodear.com/public/thirdparty/respond/dest/respond.min.js
http/1.1
1122.457999998
1547.2489999956
2634
4596
200
application/javascript
Script
http://www.dodear.com/public/responsive/images/logo/logo.png
http/1.1
1971.5530000103
2179.6829999948
13719
13371
200
image/png
Image
http://www.dodear.com/public/common/images/theme/sections/videos.png
http/1.1
1977.5360000203
2217.2060000012
2459
2112
200
image/png
Image
http://www.dodear.com/public/common/images/theme/sections/videos-dark.png
http/1.1
1977.7030000114
2181.5840000054
2446
2099
200
image/png
Image
http://www.dodear.com/public/responsive/js/home.js
http/1.1
1730.6500000122
1934.0179999999
8195
37921
200
application/javascript
Script
http://www.dodear.com/public/responsive/js/common.js
http/1.1
1747.686000017
1955.7970000023
6174
27508
200
application/javascript
Script
http://connect.net.pk/js/noticed.js
http/1.1
1957.1130000113
2581.8480000016
247
0
301
text/html
https://www.googletagmanager.com/gtag/js?id=UA-18695814-5
h2
1977.8170000063
1988.8009999995
41773
103219
200
application/javascript
Script
http://www.dodear.com/public/assets/bootstrap/js/bootstrap.min.js
http/1.1
1761.9810000178
1969.2009999999
10245
37045
200
application/javascript
Script
http://www.dodear.com/public/fonts/TitilliumWeb-Regular.woff
http/1.1
1985.531000013
3015.9259999928
24086
23736
200
font/x-woff
Font
http://www.dodear.com/public/common/images/icons/menu.png
http/1.1
2004.0610000142
2205.0429999945
1317
971
200
image/png
Image
https://www.connect.net.pk/js/noticed.js
h2
2582.0890000032
3387.9880000022
773
660
200
application/javascript
Script
http://www.connect.net.pk/modules/site/components/notice.php?jsonp_callback=jQuery32108332810219723499_1629289923802&_=1629289923803
http/1.1
3392.4270000134
3799.136000016
355
0
301
text/html
https://www.google-analytics.com/analytics.js
h2
3422.298999998
3427.3430000176
20324
49389
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j92&a=1792871424&t=pageview&_s=1&dl=http%3A%2F%2Fwww.dodear.com%2Fen%2Fhome&ul=en-us&de=UTF-8&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=1716946297&gjid=749335872&cid=1422099663.1629289925&tid=UA-18695814-5&_gid=1048098244.1629289925&_r=1&gtm=2ou8g0&z=1834320375
h2
3447.9500000016
3452.0330000087
639
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j92&tid=UA-18695814-5&cid=1422099663.1629289925&jid=1716946297&gjid=749335872&_gid=1048098244.1629289925&_u=YEBAAUAAAAAAAC~&z=1241540865
h2
3453.8830000092
3456.8490000092
712
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j92&tid=UA-18695814-5&cid=1422099663.1629289925&jid=1716946297&_u=YEBAAUAAAAAAAC~&z=470951413
h2
3458.4259999974
3466.837999993
700
42
200
image/gif
Image
https://www.connect.net.pk/modules/site/components/notice.php?jsonp_callback=jQuery32108332810219723499_1629289923802&_=1629289923803
h2
3799.3720000086
4032.0650000067
1036
0
404
text/html
Script
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)
1117.285
7.275
1753.211
14.121
1976.998
6.622
1983.629
8.297
2002.038
9.544
3394.462
5.419
3400.086
7.18
3410.705
8.123
3419.163
8.749
3436.597
17.327
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

Properly size images — Potential savings of 4 KiB
Images can slow down the page's load time. Dodear.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://www.dodear.com/public/responsive/images/logo/logo.png
13371
4106
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Dodear.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 5 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Dodear.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.dodear.com/public/responsive/css/style.css
18633
5056
Minify JavaScript — Potential savings of 5 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Dodear.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.dodear.com/public/responsive/js/common.js
6174
2549
http://www.dodear.com/public/responsive/js/home.js
8195
2319
Reduce unused CSS — Potential savings of 37 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Dodear.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.dodear.com/public/assets/bootstrap/css/bootstrap.min.css
20022
19579
http://www.dodear.com/public/responsive/css/style.css
18633
17889
Reduce unused JavaScript — Potential savings of 22 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-18695814-5
41773
22160
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 270 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://www.dodear.com/en/home
265.626
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
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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://www.dodear.com/public/responsive/images/logo/logo.png
0

Diagnostics

Avoids enormous network payloads — Total size was 218 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-18695814-5
41773
http://www.dodear.com/public/assets/jquery/jquery-3.2.1.min.js
30624
http://www.dodear.com/public/fonts/TitilliumWeb-Regular.woff
24086
https://www.google-analytics.com/analytics.js
20324
http://www.dodear.com/public/assets/bootstrap/css/bootstrap.min.css
20022
http://www.dodear.com/public/responsive/css/style.css
18633
http://www.dodear.com/public/responsive/images/logo/logo.png
13719
http://www.dodear.com/public/assets/bootstrap/js/bootstrap.min.js
10245
http://www.dodear.com/public/responsive/js/home.js
8195
http://www.dodear.com/public/assets/font-awesome/css/font-awesome.min.css
7381
Avoids an excessive DOM size — 69 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
69
Maximum DOM Depth
Videos
15
Maximum Child Elements
body
11
Avoid chaining critical requests — 10 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Dodear.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
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.
Minimizes main-thread work — 0.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
79.12
Other
36.161
Style & Layout
17.213
Parse HTML & CSS
14.829
Script Parsing & Compilation
9.87
Rendering
4.564
Garbage Collection
1.604
Keep request counts low and transfer sizes small — 27 requests • 218 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
27
223420
Script
9
121778
Stylesheet
5
48305
Font
1
24086
Image
5
20641
Document
1
5964
Other
6
2646
Media
0
0
Third-party
9
66559
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)
SHOW DETAILS
41773
0
SHOW DETAILS
20963
0
SHOW DETAILS
712
0
SHOW DETAILS
700
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
img
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
Recent Update
0.00036514330943931
Copyrights © 2021 Dodear.com.
0.00021297210847049
DoDear is not responsible for the content of external internet sites
0.0001742499069304
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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

Speed Index — 1.7 s
The time taken for the page contents to be visibly populated.

Opportunities

Eliminate render-blocking resources — Potential savings of 630 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Dodear.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://www.dodear.com/public/assets/bootstrap/css/bootstrap.min.css
20022
150
http://www.dodear.com/public/assets/font-awesome/css/font-awesome.min.css
7381
150
http://www.dodear.com/public/responsive/css/style.css
18633
190
http://www.dodear.com/public/thirdparty/circular_carousel/css/style.css
1475
110
http://www.dodear.com/public/responsive/css/skin-2.css
794
110
http://www.dodear.com/public/assets/jquery/jquery-3.2.1.min.js
30624
190
http://www.dodear.com/public/assets/bootstrap/js/bootstrap.min.js
10245
70
http://www.dodear.com/public/thirdparty/respond/dest/respond.min.js
2634
70
Avoid multiple page redirects — Potential savings of 380 ms
Redirects can cause additional delays before the page can begin loading. Dodear.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://dodear.com/
190
http://www.dodear.com/
190
http://www.dodear.com/en/home
0
Preload key requests — Potential savings of 150 ms
Key requests can be preloaded by using '<link rel=preload>'. Dodear.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
http://www.dodear.com/public/fonts/TitilliumWeb-Regular.woff
150

Diagnostics

Serve static assets with an efficient cache policy — 17 resources found
Dodear.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.connect.net.pk/js/noticed.js
0
773
https://www.google-analytics.com/analytics.js
7200000
20324
http://www.dodear.com/public/assets/jquery/jquery-3.2.1.min.js
86400000
30624
http://www.dodear.com/public/fonts/TitilliumWeb-Regular.woff
86400000
24086
http://www.dodear.com/public/assets/bootstrap/css/bootstrap.min.css
86400000
20022
http://www.dodear.com/public/responsive/css/style.css
86400000
18633
http://www.dodear.com/public/responsive/images/logo/logo.png
86400000
13719
http://www.dodear.com/public/assets/bootstrap/js/bootstrap.min.js
86400000
10245
http://www.dodear.com/public/responsive/js/home.js
86400000
8195
http://www.dodear.com/public/assets/font-awesome/css/font-awesome.min.css
86400000
7381
http://www.dodear.com/public/responsive/js/common.js
86400000
6174
http://www.dodear.com/public/thirdparty/respond/dest/respond.min.js
86400000
2634
http://www.dodear.com/public/common/images/theme/sections/videos.png
86400000
2459
http://www.dodear.com/public/common/images/theme/sections/videos-dark.png
86400000
2446
http://www.dodear.com/public/thirdparty/circular_carousel/css/style.css
86400000
1475
http://www.dodear.com/public/common/images/icons/menu.png
86400000
1317
http://www.dodear.com/public/responsive/css/skin-2.css
86400000
794

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)
http://www.dodear.com/public/fonts/TitilliumWeb-Regular.woff
1030.3949999798
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
http://www.dodear.com/public/common/images/theme/sections/videos.png
videos
83

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of dodear.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.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<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.

Contrast

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

Tables and lists

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

Internationalization and localization

`<html>` element has a 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"]`
Dodear.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Document doesn't have 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.
Failing Elements
html
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.

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
html

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

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.
Name Version
Bootstrap
3.3.7
jQuery
3.2.1
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 — 20 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://dodear.com/
Allowed
http://www.dodear.com/
Allowed
http://www.dodear.com/en/home
Allowed
http://www.dodear.com/public/assets/bootstrap/css/bootstrap.min.css
Allowed
http://www.dodear.com/public/assets/font-awesome/css/font-awesome.min.css
Allowed
http://www.dodear.com/public/responsive/css/style.css
Allowed
http://www.dodear.com/public/thirdparty/circular_carousel/css/style.css
Allowed
http://www.dodear.com/public/responsive/css/skin-2.css
Allowed
http://www.dodear.com/public/assets/jquery/jquery-3.2.1.min.js
Allowed
http://www.dodear.com/public/thirdparty/respond/dest/respond.min.js
Allowed
http://www.dodear.com/public/responsive/images/logo/logo.png
Allowed
http://www.dodear.com/public/common/images/theme/sections/videos.png
Allowed
http://www.dodear.com/public/common/images/theme/sections/videos-dark.png
Allowed
http://www.dodear.com/public/responsive/js/home.js
Allowed
http://www.dodear.com/public/responsive/js/common.js
Allowed
http://connect.net.pk/js/noticed.js
Allowed
http://www.dodear.com/public/assets/bootstrap/js/bootstrap.min.js
Allowed
http://www.dodear.com/public/fonts/TitilliumWeb-Regular.woff
Allowed
http://www.dodear.com/public/common/images/icons/menu.png
Allowed
http://www.connect.net.pk/modules/site/components/notice.php?jsonp_callback=jQuery32108332810219723499_1629289923802&_=1629289923803
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 8 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
SHOW DETAILS
5
Medium
SHOW DETAILS
3
Medium

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

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
SHOW DETAILS
Failed to load resource: the server responded with a status of 404 (Not Found)
SHOW DETAILS
Failed to load resource: the server responded with a status of 404 (Not Found)
82

SEO

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

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.

Content Best Practices

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.

Content Best Practices

Document doesn't have 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.
Failing Elements
html
Document does not have 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.

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

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 dodear.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 dodear.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.
Redirects 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) 56
Performance 59
Accessibility 60
Best Practices 67
SEO 69
Progressive Web App 25
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://www.dodear.com/en/home
Updated: 21st June, 2021

2.16 seconds
First Contentful Paint (FCP)
67%
19%
14%

0.02 seconds
First Input Delay (FID)
96%
4%
0%

Simulate loading on mobile
59

Performance

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

Metrics

Total Blocking Time — 60 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.073
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Dodear.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Dodear.com should consider lazy-loading offscreen and hidden images.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 270 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://www.dodear.com/en/home
268.985
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
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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://files.dodear.com//ads/1272895978.gif
0

Diagnostics

Avoids an excessive DOM size — 75 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
75
Maximum DOM Depth
Videos
15
Maximum Child Elements
body
11
Avoid chaining critical requests — 10 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Dodear.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.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)
http://www.dodear.com/en/home
260.212
15.192
8.844
http://www.dodear.com/public/assets/jquery/jquery-3.2.1.min.js
250.58
185.884
6.524
Unattributable
250.252
17.784
1.044
https://www.google-analytics.com/analytics.js
162.544
143.94
5.828
https://www.googletagmanager.com/gtag/js?id=UA-18695814-5
103.756
88.672
10.712
http://www.dodear.com/public/responsive/js/common.js
72.956
22.388
4.6
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
528.408
Other
326.516
Style & Layout
194.528
Parse HTML & CSS
91.252
Script Parsing & Compilation
50.204
Rendering
42.528
Keep request counts low and transfer sizes small — 28 requests • 3,751 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
28
3840707
Image
6
3642594
Script
9
116921
Stylesheet
5
48305
Font
1
24086
Document
1
6203
Other
6
2598
Media
0
0
Third-party
9
61693
Minimize third-party usage — Third-party code blocked the main thread for 90 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)
SHOW DETAILS
20860
79.808
SHOW DETAILS
37019
6.94
SHOW DETAILS
712
0
SHOW DETAILS
700
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
img
Avoid large layout shifts — 4 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
Copyrights © 2021 Dodear.com. DoDear is not responsible for the content of ext…
0.072593154907227
Recent Update
0.0014990565612229
Copyrights © 2021 Dodear.com.
0.00058430782667085
DoDear is not responsible for the content of external internet sites
0.00047807004000342
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 3 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-analytics.com/analytics.js
4167
141
http://www.dodear.com/public/assets/jquery/jquery-3.2.1.min.js
3720
70
https://www.googletagmanager.com/gtag/js?id=UA-18695814-5
3028
59
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.

Other

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://dodear.com/
http/1.1
0
220.29000008479
323
0
301
text/html
http://www.dodear.com/
http/1.1
220.92100000009
453.84699990973
331
0
302
text/html
http://www.dodear.com/en/home
http/1.1
454.62299999781
722.61000005528
6203
11949
200
text/html
Document
http://www.dodear.com/public/assets/bootstrap/css/bootstrap.min.css
http/1.1
741.91799992695
990.0599999819
20022
121200
200
text/css
Stylesheet
http://www.dodear.com/public/assets/font-awesome/css/font-awesome.min.css
http/1.1
742.1359999571
957.85699994303
7381
31000
200
text/css
Stylesheet
http://www.dodear.com/public/responsive/css/style.css
http/1.1
742.50599998049
1394.1389999818
18633
110000
200
text/css
Stylesheet
http://www.dodear.com/public/thirdparty/circular_carousel/css/style.css
http/1.1
742.973000044
964.86800001003
1475
3787
200
text/css
Stylesheet
http://www.dodear.com/public/responsive/css/skin-2.css
http/1.1
743.41000011191
1212.1699999552
794
1047
200
text/css
Stylesheet
http://www.dodear.com/public/assets/jquery/jquery-3.2.1.min.js
http/1.1
743.71699988842
1360.4580000974
30624
86659
200
application/javascript
Script
http://www.dodear.com/public/thirdparty/respond/dest/respond.min.js
http/1.1
743.91600000672
960.93700011261
2634
4596
200
application/javascript
Script
http://www.dodear.com/public/responsive/images/logo/logo.png
http/1.1
1673.4559999313
1906.4160000999
13719
13371
200
image/png
Image
http://www.dodear.com/public/common/images/theme/sections/videos.png
http/1.1
1683.1149999052
1920.2920000535
2459
2112
200
image/png
Image
http://www.dodear.com/public/common/images/theme/sections/videos-dark.png
http/1.1
1683.4060000256
1896.7510000803
2446
2099
200
image/png
Image
http://files.dodear.com//ads/1272895978.gif
http/1.1
1683.5960000753
8068.5159999412
3621953
3621724
200
image/gif
Image
http://www.dodear.com/public/responsive/js/home.js
http/1.1
1369.410000043
1576.3850000221
8195
37921
200
application/javascript
Script
http://www.dodear.com/public/responsive/js/common.js
http/1.1
1395.8950000815
1622.8219999466
6174
27508
200
application/javascript
Script
http://connect.net.pk/js/noticed.js
http/1.1
1624.0979998838
3854.6370000113
250
0
301
text/html
https://www.googletagmanager.com/gtag/js?id=UA-18695814-5
h2
1683.7539998814
1719.1439999733
37019
91514
200
application/javascript
Script
http://www.dodear.com/public/assets/bootstrap/js/bootstrap.min.js
http/1.1
1418.5269998852
1669.4370000623
10245
37045
200
application/javascript
Script
http://www.dodear.com/public/common/images/icons/menu.png
http/1.1
1692.1510000248
1912.2339999303
1317
971
200
image/png
Image
http://www.dodear.com/public/fonts/TitilliumWeb-Regular.woff
http/1.1
1700.1149998978
2168.1129999924
24086
23736
200
font/x-woff
Font
https://www.connect.net.pk/js/noticed.js
h2
3855.0319999922
4076.4309999067
773
660
200
application/javascript
Script
http://www.connect.net.pk/modules/site/components/notice.php?jsonp_callback=jQuery32107825706814195001_1624258777638&_=1624258777639
http/1.1
4083.8069999591
6517.2639999073
343
0
301
text/html
https://www.google-analytics.com/analytics.js
h2
4137.2090000659
4147.5859999191
20221
49153
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=1423904577&t=pageview&_s=1&dl=http%3A%2F%2Fwww.dodear.com%2Fen%2Fhome&ul=en-us&de=UTF-8&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=950925135&gjid=407731432&cid=865491252.1624258780&tid=UA-18695814-5&_gid=1200629256.1624258780&_r=1&gtm=2ou6g0&z=1943031552
h2
4187.5479998998
4191.6680000722
639
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j90&tid=UA-18695814-5&cid=865491252.1624258780&jid=950925135&gjid=407731432&_gid=1200629256.1624258780&_u=YEBAAUAAAAAAAC~&z=1604590334
h2
4194.9030000251
4198.5349999741
712
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j90&tid=UA-18695814-5&cid=865491252.1624258780&jid=950925135&_u=YEBAAUAAAAAAAC~&z=1517865018
h2
4201.4999999665
4209.7499999218
700
42
200
image/gif
Image
https://www.connect.net.pk/modules/site/components/notice.php?jsonp_callback=jQuery32107825706814195001_1624258777638&_=1624258777639
h2
6517.4990000669
6751.0609999299
1036
0
404
text/html
Script
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)
737.959
8.836
999.404
5.548
1403.486
5.328
1408.913
17.402
1681.326
10.831
1692.176
18.35
1710.79
5.298
1716.206
7.833
1724.147
19.079
4086.154
8.681
4095.339
9.458
4110.307
20.029
4130.781
14.718
4161.188
35.347
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

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

Other

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

Opportunities

Minify CSS — Potential savings of 5 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Dodear.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.dodear.com/public/responsive/css/style.css
18633
5056
Minify JavaScript — Potential savings of 5 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Dodear.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.dodear.com/public/responsive/js/common.js
6174
2549
http://www.dodear.com/public/responsive/js/home.js
8195
2319
Reduce unused CSS — Potential savings of 37 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Dodear.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.dodear.com/public/assets/bootstrap/css/bootstrap.min.css
20022
19515
http://www.dodear.com/public/responsive/css/style.css
18633
17910
Preload key requests — Potential savings of 480 ms
Key requests can be preloaded by using '<link rel=preload>'. Dodear.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
http://www.dodear.com/public/fonts/TitilliumWeb-Regular.woff
480

Diagnostics

Avoid enormous network payloads — Total size was 3,751 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://files.dodear.com//ads/1272895978.gif
3621953
https://www.googletagmanager.com/gtag/js?id=UA-18695814-5
37019
http://www.dodear.com/public/assets/jquery/jquery-3.2.1.min.js
30624
http://www.dodear.com/public/fonts/TitilliumWeb-Regular.woff
24086
https://www.google-analytics.com/analytics.js
20221
http://www.dodear.com/public/assets/bootstrap/css/bootstrap.min.css
20022
http://www.dodear.com/public/responsive/css/style.css
18633
http://www.dodear.com/public/responsive/images/logo/logo.png
13719
http://www.dodear.com/public/assets/bootstrap/js/bootstrap.min.js
10245
http://www.dodear.com/public/responsive/js/home.js
8195

Metrics

Speed Index — 10.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 22.5 s
The timing of the largest text or image that is painted.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,730 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Dodear.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://www.dodear.com/public/assets/bootstrap/css/bootstrap.min.css
20022
780
http://www.dodear.com/public/assets/font-awesome/css/font-awesome.min.css
7381
480
http://www.dodear.com/public/responsive/css/style.css
18633
780
http://www.dodear.com/public/thirdparty/circular_carousel/css/style.css
1475
330
http://www.dodear.com/public/responsive/css/skin-2.css
794
330
http://www.dodear.com/public/assets/jquery/jquery-3.2.1.min.js
30624
930
http://www.dodear.com/public/assets/bootstrap/js/bootstrap.min.js
10245
180
http://www.dodear.com/public/thirdparty/respond/dest/respond.min.js
2634
180
Avoid multiple page redirects — Potential savings of 1,260 ms
Redirects can cause additional delays before the page can begin loading. Dodear.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://dodear.com/
630
http://www.dodear.com/
630
http://www.dodear.com/en/home
0
Use video formats for animated content — Potential savings of 3,183 KiB
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.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://files.dodear.com//ads/1272895978.gif
3621724
3259552

Diagnostics

Serve static assets with an efficient cache policy — 18 resources found
Dodear.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://files.dodear.com//ads/1272895978.gif
0
3621953
https://www.connect.net.pk/js/noticed.js
0
773
https://www.google-analytics.com/analytics.js
7200000
20221
http://www.dodear.com/public/assets/jquery/jquery-3.2.1.min.js
86400000
30624
http://www.dodear.com/public/fonts/TitilliumWeb-Regular.woff
86400000
24086
http://www.dodear.com/public/assets/bootstrap/css/bootstrap.min.css
86400000
20022
http://www.dodear.com/public/responsive/css/style.css
86400000
18633
http://www.dodear.com/public/responsive/images/logo/logo.png
86400000
13719
http://www.dodear.com/public/assets/bootstrap/js/bootstrap.min.js
86400000
10245
http://www.dodear.com/public/responsive/js/home.js
86400000
8195
http://www.dodear.com/public/assets/font-awesome/css/font-awesome.min.css
86400000
7381
http://www.dodear.com/public/responsive/js/common.js
86400000
6174
http://www.dodear.com/public/thirdparty/respond/dest/respond.min.js
86400000
2634
http://www.dodear.com/public/common/images/theme/sections/videos.png
86400000
2459
http://www.dodear.com/public/common/images/theme/sections/videos-dark.png
86400000
2446
http://www.dodear.com/public/thirdparty/circular_carousel/css/style.css
86400000
1475
http://www.dodear.com/public/common/images/icons/menu.png
86400000
1317
http://www.dodear.com/public/responsive/css/skin-2.css
86400000
794
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)
http://www.dodear.com/public/fonts/TitilliumWeb-Regular.woff
467.99800009467

Other

First Contentful Paint (3G) — 5578 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
60

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of dodear.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.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<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 `[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.

Contrast

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

Tables and lists

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

Internationalization and localization

`<html>` element has a 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"]`
Dodear.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Document doesn't have 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.
Failing Elements
html
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
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.

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
html

Manual Checks

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

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.
Name Version
Bootstrap
3.3.7
jQuery
3.2.1
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 — 21 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://dodear.com/
Allowed
http://www.dodear.com/
Allowed
http://www.dodear.com/en/home
Allowed
http://www.dodear.com/public/assets/bootstrap/css/bootstrap.min.css
Allowed
http://www.dodear.com/public/assets/font-awesome/css/font-awesome.min.css
Allowed
http://www.dodear.com/public/responsive/css/style.css
Allowed
http://www.dodear.com/public/thirdparty/circular_carousel/css/style.css
Allowed
http://www.dodear.com/public/responsive/css/skin-2.css
Allowed
http://www.dodear.com/public/assets/jquery/jquery-3.2.1.min.js
Allowed
http://www.dodear.com/public/thirdparty/respond/dest/respond.min.js
Allowed
http://www.dodear.com/public/responsive/images/logo/logo.png
Allowed
http://www.dodear.com/public/common/images/theme/sections/videos.png
Allowed
http://www.dodear.com/public/common/images/theme/sections/videos-dark.png
Allowed
http://files.dodear.com//ads/1272895978.gif
Allowed
http://www.dodear.com/public/responsive/js/home.js
Allowed
http://www.dodear.com/public/responsive/js/common.js
Allowed
http://connect.net.pk/js/noticed.js
Allowed
http://www.dodear.com/public/assets/bootstrap/js/bootstrap.min.js
Allowed
http://www.dodear.com/public/common/images/icons/menu.png
Allowed
http://www.dodear.com/public/fonts/TitilliumWeb-Regular.woff
Allowed
http://www.connect.net.pk/modules/site/components/notice.php?jsonp_callback=jQuery32107825706814195001_1624258777638&_=1624258777639
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 8 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
SHOW DETAILS
5
Medium
SHOW DETAILS
3
Medium

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
http://files.dodear.com//ads/1272895978.gif
302 x 252
320 x 267
604 x 504
http://www.dodear.com/public/responsive/images/logo/logo.png
148 x 50
178 x 60
296 x 100

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

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
SHOW DETAILS
Failed to load resource: the server responded with a status of 404 (Not Found)
69

SEO

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

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.

Content Best Practices

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
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.

Content Best Practices

Document doesn't have 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.
Failing Elements
html
Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

Mobile Friendly

Document doesn't use legible font sizes — 44.26% 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
SHOW DETAILS
.text-size-x-small
55.74%
10.24px
SHOW DETAILS
44.26%
≥ 12px

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 dodear.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 dodear.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: 192.168.20.52
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Metro Ethernet Network
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
Wild West Domains, LLC 23.48.203.144
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 70/100
WOT Child Safety: 97/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
dodear.com. 192.168.20.51 IN 3600
dodear.com. 192.168.20.52 IN 3600

NS Records

Host Nameserver Class TTL
dodear.com. ns17.domaincontrol.com. IN 3600
dodear.com. ns18.domaincontrol.com. IN 3600

MX Records

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

SOA Records

Domain Name Primary NS Responsible Email TTL
dodear.com. ns17.domaincontrol.com. dns.jomax.net. 3600

TXT Records

Host Value Class TTL
dodear.com. google-site-verification=G-Iwn-tEHStT6pNPjMznOvMXt5avBOiAWsXd8gptrGU IN 3600
dodear.com. NETORGFT12916008.onmicrosoft.com IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 404 Not Found
Content-Type: text/html; charset=UTF-8
Server:
Date: 30th August, 2021
Content-Length: 0

Whois Lookup

Created: 18th January, 2007
Changed: 17th September, 2019
Expires: 18th January, 2028
Registrar: Wild West Domains, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns17.domaincontrol.com
ns18.domaincontrol.com
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
100 S. Mill Ave, Suite 1600
Owner Post Code: 85281
Owner City: Tempe
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: Select Contact Domain Holder link at https://www.secureserver.net/whois?plid=1387&domain=DODEAR.COM
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
100 S. Mill Ave, Suite 1600
Admin Post Code: 85281
Admin City: Tempe
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: Select Contact Domain Holder link at https://www.secureserver.net/whois?plid=1387&domain=DODEAR.COM
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
100 S. Mill Ave, Suite 1600
Tech Post Code: 85281
Tech City: Tempe
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: Select Contact Domain Holder link at https://www.secureserver.net/whois?plid=1387&domain=DODEAR.COM
Full Whois: Domain Name: DODEAR.COM
Registry Domain ID: 762404796_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.wildwestdomains.com
Registrar URL: https://www.wildwestdomains.com
Updated Date: 2019-09-17T07:22:31Z
Creation Date: 2007-01-18T08:31:55Z
Registrar Registration Expiration Date: 2028-01-18T08:31:55Z
Registrar: Wild West Domains, LLC
Registrar IANA ID: 440
Registrar Abuse Contact Email: abuse@wildwestdomains.com
Registrar Abuse Contact Phone: +1.4806242505
Reseller: Domains Priced Right
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 100 S. Mill Ave, Suite 1600
Registrant City: Tempe
Registrant State/Province: Arizona
Registrant Postal Code: 85281
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: Select Contact Domain Holder link at https://www.secureserver.net/whois?plid=1387&domain=DODEAR.COM
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 100 S. Mill Ave, Suite 1600
Admin City: Tempe
Admin State/Province: Arizona
Admin Postal Code: 85281
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: Select Contact Domain Holder link at https://www.secureserver.net/whois?plid=1387&domain=DODEAR.COM
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 100 S. Mill Ave, Suite 1600
Tech City: Tempe
Tech State/Province: Arizona
Tech Postal Code: 85281
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: Select Contact Domain Holder link at https://www.secureserver.net/whois?plid=1387&domain=DODEAR.COM
Name Server: NS17.DOMAINCONTROL.COM
Name Server: NS18.DOMAINCONTROL.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-06-05T23:46:07Z <<<
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.

View Raw Whois

Nameservers

Name IP Address
ns17.domaincontrol.com 97.74.108.9
ns18.domaincontrol.com 173.201.76.9
Related

Subdomains

Domain Subdomain
english.dodear.com
english
torrents.dodear.com
torrents

Similar Sites

Domain Valuation Snoop Score
indiafm.com
$12,857 USD 3/5
jang.com.pk
$4,406,667 USD 4/5
juniorspk.com
0/5
mp3pk.net
0/5
onlinegames.net
$9,185 USD 2/5
All sites similar to dodear.com

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
dodear.info
0/5
dodear.net
$91 USD 1/5
dodear.net.pk
0/5
dodear.org
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
domaze.net
$3,896 USD 2/5
Love W3 Snoop?
Update Now

dodear.com Infographic

dodear.com by the numbers infographic

Recently Updated

xbox.com
techent.tv
tvsarawak.com
asianewstoday.com
theiskandarian.com
zulyusmar.com
suaramerdeka.com.my
buletin.my
300mbmovies4u.co
hackinstaaccount.com

Recently Viewed

lugare.com
lhsaigon.com
neotypestation.com
lqipnr.com
lightwriterblue.com
manekare.com
nessaandjordan.com
opticaliillusions.com
ooiiwa.com
ringsistanbul.com