dttsonline.com

dttsonline.com is SSL secured

Free website and domain report on dttsonline.com

Last Updated: 24th August, 2021 Update Now
Overview

Snoop Summary for dttsonline.com

This is a free and comprehensive report about dttsonline.com. The domain dttsonline.com is currently hosted on a server located in Iran with the IP address 185.78.20.241, where the local currency is IRR and Persian is the local language. Dttsonline.com is expected to earn an estimated $39 USD per day from advertising revenue. The sale of dttsonline.com would possibly be worth $28,124 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Dttsonline.com receives an estimated 9,107 unique visitors every day - a huge amount of traffic! This report was last updated 24th August, 2021.

About dttsonline.com

Site Preview: dttsonline.com dttsonline.com
Title: PASARGAD TRADER | LOGIN
Description:
Keywords and Tags: business
Related Terms:
Fav Icon:
Age: Over 9 years old
Domain Created: 11th April, 2014
Domain Updated: 31st March, 2021
Domain Expires: 11th April, 2022
Review

Snoop Score

3/5 (Great!)

Valuation

$28,124 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 47,194
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 9,107
Monthly Visitors: 277,188
Yearly Visitors: 3,324,055
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $39 USD
Monthly Revenue: $1,172 USD
Yearly Revenue: $14,057 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: dttsonline.com 14
Domain Name: dttsonline 10
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 61
Performance 92
Accessibility 54
Best Practices 73
SEO 70
Progressive Web App 18
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.dttsonline.com/dtts/dtts/customer/login.jsp
Updated: 24th August, 2021

1.57 seconds
First Contentful Paint (FCP)
80%
11%
9%

0.01 seconds
First Input Delay (FID)
95%
2%
3%

Simulate loading on desktop
92

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 0.7 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.7 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.032
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.7 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://dttsonline.com/
http/1.1
0
417.49000002164
261
0
301
text/html
https://www.dttsonline.com/
http/1.1
418.1170000229
1833.0330000026
299
0
302
text/html
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
http/1.1
1833.6730001029
2824.006000068
3181
10136
200
text/html
Document
https://www.dttsonline.com/dtts/dtts/customer/lib/bowser.min.js
http/1.1
2841.6370000923
4205.721000093
2608
6790
200
application/javascript
Script
https://www.dttsonline.com/dtts/dtts/customer/assets/css/login.css?v=12.0.7
http/1.1
2841.9520000461
4218.6720001046
33925
104278
200
text/css
Stylesheet
https://www.dttsonline.com/dtts/dtts/customer/assets/js/keyboard.js?v=12.0.1
http/1.1
2842.3510000575
4205.129000009
5887
20836
200
application/javascript
Script
https://www.dttsonline.com/dtts/dtts/customer/assets/css/keyboard.css?v=12.0.1
http/1.1
2842.638000031
4233.3990000188
1376
6053
200
text/css
Stylesheet
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/logoCenter.png
http/1.1
4230.7760000695
5204.8520001117
19423
19204
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-google-play.png
http/1.1
4231.0140000191
5594.933000044
19210
18991
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-datxsoft-ios.png
http/1.1
4231.1990000308
5623.1630000984
13700
13481
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-cafebazaar.png
http/1.1
4231.4900000347
5232.2120000608
14459
14240
200
image/png
Image
https://www.dttsonline.com/dtts/sCaptcha.png
http/1.1
4231.8080000114
5594.4820001023
1586
1393
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/FF4D00-0.png
http/1.1
4231.9800000405
5011.5280000027
309
95
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/js/js.js?v=12.0.1
http/1.1
4221.3240000419
5041.060000076
1408
4179
200
application/javascript
Script
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/lbg.jpg
http/1.1
4237.9280000459
5979.4320000801
267141
266919
200
image/jpeg
Image
data
4242.44000006
4242.5190000795
0
451
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/fonts/BYekan.ttf
http/1.1
4245.1270000311
5793.6029999983
52466
52232
200
application/octet-stream
Font
data
4248.4580000164
4248.8160000648
0
18650
200
image/png
Image
data
4249.2220000131
4249.2810001131
0
1449
200
image/png
Image
data
4249.5360000758
4249.6000000974
0
1333
200
image/png
Image
data
4250.4010000266
4250.5880000535
0
7082
200
image/png
Image
data
4251.5330000315
4251.7700000899
0
9388
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/keyboard.png
http/1.1
5984.328999999
6763.3230000501
1280
1063
200
image/png
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
2837.515
9.908
4232.186
10.297
4245.45
47.739
4295.26
6.307
4319.627
5.141
5806.873
12.207
5991.042
5.379
6023.56
70.403
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 43 KiB
Images can slow down the page's load time. Dttsonline.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-google-play.png
18991
17824
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-cafebazaar.png
14240
13365
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-datxsoft-ios.png
13481
12653
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Dttsonline.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Dttsonline.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Dttsonline.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 14 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Dttsonline.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)
https://www.dttsonline.com/dtts/dtts/customer/assets/css/login.css?v=12.0.7
33925
14299
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images — Potential savings of 54 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/lbg.jpg
266919
55504
Serve images in next-gen formats — Potential savings of 179 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/lbg.jpg
266919
158943
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/logoCenter.png
19204
13506
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-google-play.png
18991
11255
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Dttsonline.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
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.

Diagnostics

Avoids enormous network payloads — Total size was 428 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/lbg.jpg
267141
https://www.dttsonline.com/dtts/dtts/customer/assets/fonts/BYekan.ttf
52466
https://www.dttsonline.com/dtts/dtts/customer/assets/css/login.css?v=12.0.7
33925
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/logoCenter.png
19423
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-google-play.png
19210
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-cafebazaar.png
14459
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-datxsoft-ios.png
13700
https://www.dttsonline.com/dtts/dtts/customer/assets/js/keyboard.js?v=12.0.1
5887
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
3181
https://www.dttsonline.com/dtts/dtts/customer/lib/bowser.min.js
2608
Avoids an excessive DOM size — 88 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
88
Maximum DOM Depth
img
7
Maximum Child Elements
8
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Dttsonline.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.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
201.327
4.054
1.162
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Rendering
99.117
Style & Layout
63.571
Other
53.303
Script Evaluation
19.523
Parse HTML & CSS
10.283
Script Parsing & Compilation
4.413
Keep request counts low and transfer sizes small — 17 requests • 428 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
17
438519
Image
8
337108
Font
1
52466
Stylesheet
2
35301
Script
3
9903
Document
1
3181
Other
2
560
Media
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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
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 — 2 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Opportunities

Eliminate render-blocking resources — Potential savings of 260 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Dttsonline.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)
https://www.dttsonline.com/dtts/dtts/customer/assets/css/login.css?v=12.0.7
33925
150
https://www.dttsonline.com/dtts/dtts/customer/assets/css/keyboard.css?v=12.0.1
1376
150
https://www.dttsonline.com/dtts/dtts/customer/lib/bowser.min.js
2608
150
https://www.dttsonline.com/dtts/dtts/customer/assets/js/keyboard.js?v=12.0.1
5887
150
Avoid multiple page redirects — Potential savings of 420 ms
Redirects can cause additional delays before the page can begin loading. Dttsonline.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://dttsonline.com/
190
https://www.dttsonline.com/
230
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
0

Metrics

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

Opportunities

Reduce initial server response time — Root document took 990 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
991.33

Diagnostics

Serve static assets with an efficient cache policy — 13 resources found
Dttsonline.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.dttsonline.com/dtts/dtts/customer/assets/imgs/lbg.jpg
0
267141
https://www.dttsonline.com/dtts/dtts/customer/assets/fonts/BYekan.ttf
0
52466
https://www.dttsonline.com/dtts/dtts/customer/assets/css/login.css?v=12.0.7
0
33925
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/logoCenter.png
0
19423
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-google-play.png
0
19210
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-cafebazaar.png
0
14459
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-datxsoft-ios.png
0
13700
https://www.dttsonline.com/dtts/dtts/customer/assets/js/keyboard.js?v=12.0.1
0
5887
https://www.dttsonline.com/dtts/dtts/customer/lib/bowser.min.js
0
2608
https://www.dttsonline.com/dtts/dtts/customer/assets/js/js.js?v=12.0.1
0
1408
https://www.dttsonline.com/dtts/dtts/customer/assets/css/keyboard.css?v=12.0.1
0
1376
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/keyboard.png
0
1280
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/FF4D00-0.png
0
309
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.dttsonline.com/dtts/dtts/customer/assets/fonts/BYekan.ttf
1548.4759999672
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
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/logoCenter.png
img
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-google-play.png
img
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-cafebazaar.png
img
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-datxsoft-ios.png
img
https://www.dttsonline.com/dtts/sCaptcha.png
img
54

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of dttsonline.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.

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Navigation

Some elements have 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.
Failing Elements

Manual Checks

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

Best Practices

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

Audits

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

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://dttsonline.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

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
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/FF4D00-0.png
25 x 25
1 x 1
25 x 25

Audits

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

SEO

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

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
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.

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.

Mobile Friendly

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dttsonline.com on mobile screens.

Content Best Practices

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
img
img
img
img

Manual Checks

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

Progressive Web App

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

PWA Optimized

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

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dttsonline.com on mobile screens.
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) 57
Performance 81
Accessibility 54
Best Practices 73
SEO 58
Progressive Web App 17
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.dttsonline.com/dtts/dtts/customer/login.jsp
Updated: 24th August, 2021

2.82 seconds
First Contentful Paint (FCP)
55%
24%
21%

0.25 seconds
First Input Delay (FID)
1%
95%
4%

Simulate loading on mobile
81

Performance

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

Metrics

Time to Interactive — 2.8 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0.099
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. Dttsonline.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Dttsonline.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Dttsonline.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Dttsonline.com should consider minifying JS files.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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.
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.

Diagnostics

Avoids enormous network payloads — Total size was 428 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/lbg.jpg
267141
https://www.dttsonline.com/dtts/dtts/customer/assets/fonts/BYekan.ttf
52466
https://www.dttsonline.com/dtts/dtts/customer/assets/css/login.css?v=12.0.7
33925
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/logoCenter.png
19423
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-google-play.png
19210
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-cafebazaar.png
14459
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-datxsoft-ios.png
13700
https://www.dttsonline.com/dtts/dtts/customer/assets/js/keyboard.js?v=12.0.1
5887
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
3181
https://www.dttsonline.com/dtts/dtts/customer/lib/bowser.min.js
2608
Avoids an excessive DOM size — 88 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
88
Maximum DOM Depth
img
7
Maximum Child Elements
8
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Dttsonline.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
2016.416
14.196
4.76
Unattributable
318.184
13.088
0.944
https://www.dttsonline.com/dtts/dtts/customer/assets/js/keyboard.js?v=12.0.1
52.096
35.816
9.32
Keep request counts low and transfer sizes small — 17 requests • 428 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
17
438657
Image
8
337282
Font
1
52466
Stylesheet
2
35301
Script
3
9903
Document
1
3181
Other
2
524
Media
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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
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 — 7 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.dttsonline.com/dtts/dtts/customer/login.jsp
2430
402
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
1837
289
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
2126
221
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
1605
210
Unattributable
630
202
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
2347
83
https://www.dttsonline.com/dtts/dtts/customer/assets/js/keyboard.js?v=12.0.1
2832
53
Avoid non-composited animations — 2 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name

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://dttsonline.com/
http/1.1
0
223.99500012398
249
0
301
text/html
https://www.dttsonline.com/
http/1.1
224.45300035179
1053.2189998776
275
0
302
text/html
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
http/1.1
1053.8950003684
2084.0159999207
3181
10136
200
text/html
Document
https://www.dttsonline.com/dtts/dtts/customer/lib/bowser.min.js
http/1.1
2100.6779996678
2883.6219999939
2608
6790
200
application/javascript
Script
https://www.dttsonline.com/dtts/dtts/customer/assets/css/login.css?v=12.0.7
http/1.1
2100.879999809
3086.0770000145
33925
104278
200
text/css
Stylesheet
https://www.dttsonline.com/dtts/dtts/customer/assets/js/keyboard.js?v=12.0.1
http/1.1
2101.1990001425
2886.0449995846
5887
20836
200
application/javascript
Script
https://www.dttsonline.com/dtts/dtts/customer/assets/css/keyboard.css?v=12.0.1
http/1.1
2101.540999487
2883.9769996703
1376
6053
200
text/css
Stylesheet
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/logoCenter.png
http/1.1
3087.786000222
3884.1220000759
19423
19204
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-google-play.png
http/1.1
3100.4600003362
4084.1859998181
19210
18991
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-datxsoft-ios.png
http/1.1
3102.4569999427
4484.4309994951
13700
13481
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-cafebazaar.png
http/1.1
3102.8079995885
4483.8380003348
14459
14240
200
image/png
Image
https://www.dttsonline.com/dtts/sCaptcha.png
http/1.1
3102.9880000278
3684.6249997616
1760
1562
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/FF4D00-0.png
http/1.1
3103.1590001658
3884.8780002445
309
95
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/js/js.js?v=12.0.1
http/1.1
2891.1049999297
3684.1770000756
1408
4179
200
application/javascript
Script
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/lbg.jpg
http/1.1
3104.8729997128
5041.4629997686
267141
266919
200
image/jpeg
Image
data
3109.1470001265
3109.2389998958
0
451
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/fonts/BYekan.ttf
http/1.1
3112.5029996037
4284.4270002097
52466
52232
200
application/octet-stream
Font
data
3118.9559996128
3119.4639997557
0
18650
200
image/png
Image
data
3119.9580002576
3120.0609998778
0
1449
200
image/png
Image
data
3120.3889995813
3120.4719999805
0
1333
200
image/png
Image
data
3121.6959999874
3121.9060001895
0
7082
200
image/png
Image
data
3122.9250002652
3123.1509996578
0
9388
200
image/png
Image
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/keyboard.png
http/1.1
5048.6669996753
5827.3999998346
1280
1063
200
image/png
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
2097.753
9.472
3099.383
13.157
3112.557
104.782
3218.398
7.001
3236.778
6.179
3242.974
50.417
4302.733
10.958
5055.15
6.451
5069.207
72.244
5141.99
110.581
5252.884
41.662
6093.702
100.41
6593.936
5.397
7085.822
7.752
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 — 2.5 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 2.6 s
The timing of the largest text or image that is painted.
Total Blocking Time — 230 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 700 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Dttsonline.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)
https://www.dttsonline.com/dtts/dtts/customer/assets/css/login.css?v=12.0.7
33925
780
https://www.dttsonline.com/dtts/dtts/customer/assets/css/keyboard.css?v=12.0.1
1376
480
https://www.dttsonline.com/dtts/dtts/customer/lib/bowser.min.js
2608
480
https://www.dttsonline.com/dtts/dtts/customer/assets/js/keyboard.js?v=12.0.1
5887
630
Reduce unused CSS — Potential savings of 14 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Dttsonline.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)
https://www.dttsonline.com/dtts/dtts/customer/assets/css/login.css?v=12.0.7
33925
14256
Efficiently encode images — Potential savings of 54 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/lbg.jpg
266919
55504
Serve images in next-gen formats — Potential savings of 179 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/lbg.jpg
266919
158943
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/logoCenter.png
19204
13506
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-google-play.png
18991
11255
Preload key requests — Potential savings of 180 ms
Key requests can be preloaded by using '<link rel=preload>'. Dttsonline.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://www.dttsonline.com/dtts/dtts/customer/assets/fonts/BYekan.ttf
180

Diagnostics

Minimize main-thread work — 2.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Rendering
1397.288
Style & Layout
474.324
Other
409.856
Script Evaluation
80.176
Parse HTML & CSS
38.828
Script Parsing & Compilation
20.152

Metrics

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

Other

Max Potential First Input Delay — 400 ms
Users could experience a delay when interacting with the page.
First Contentful Paint (3G) — 4691.5 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Reduce initial server response time — Root document took 1,030 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
1031.117
Avoid multiple page redirects — Potential savings of 1,410 ms
Redirects can cause additional delays before the page can begin loading. Dttsonline.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://dttsonline.com/
630
https://www.dttsonline.com/
780
https://www.dttsonline.com/dtts/dtts/customer/login.jsp
0

Diagnostics

Serve static assets with an efficient cache policy — 13 resources found
Dttsonline.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.dttsonline.com/dtts/dtts/customer/assets/imgs/lbg.jpg
0
267141
https://www.dttsonline.com/dtts/dtts/customer/assets/fonts/BYekan.ttf
0
52466
https://www.dttsonline.com/dtts/dtts/customer/assets/css/login.css?v=12.0.7
0
33925
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/logoCenter.png
0
19423
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-google-play.png
0
19210
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-cafebazaar.png
0
14459
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-datxsoft-ios.png
0
13700
https://www.dttsonline.com/dtts/dtts/customer/assets/js/keyboard.js?v=12.0.1
0
5887
https://www.dttsonline.com/dtts/dtts/customer/lib/bowser.min.js
0
2608
https://www.dttsonline.com/dtts/dtts/customer/assets/js/js.js?v=12.0.1
0
1408
https://www.dttsonline.com/dtts/dtts/customer/assets/css/keyboard.css?v=12.0.1
0
1376
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/keyboard.png
0
1280
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/FF4D00-0.png
0
309
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.dttsonline.com/dtts/dtts/customer/assets/fonts/BYekan.ttf
1171.9240006059
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
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/logoCenter.png
img
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-google-play.png
img
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-cafebazaar.png
img
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/badge-datxsoft-ios.png
img
https://www.dttsonline.com/dtts/sCaptcha.png
img
54

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of dttsonline.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.

ARIA

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

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Contrast

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Navigation

Some elements have 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.
Failing Elements

Manual Checks

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

Best Practices

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

Audits

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

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://dttsonline.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

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
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/logoCenter.png
320 x 153
159 x 76
640 x 306
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/FF4D00-0.png
25 x 25
1 x 1
50 x 50
https://www.dttsonline.com/dtts/dtts/customer/assets/imgs/keyboard.png
24 x 14
30 x 18
48 x 28

Audits

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

SEO

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

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
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.

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dttsonline.com on mobile screens.
Document doesn't use 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 not sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document 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
img
img
img
img

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

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 dttsonline.com. This includes details about web app manifests.

PWA Optimized

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.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not 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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of dttsonline.com on mobile screens.
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: 185.78.20.241
Continent: Asia
Country: Iran
Iran Flag
Region:
City:
Longitude: 51.4115
Latitude: 35.698
Currencies: IRR
Languages: Persian

Web Hosting Provider

Registration

Domain Registrant

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

Domain Registrar

Name IP Address
TUCOWS, INC. 199.16.172.52
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: dttsonline.com
Issued By: Certum Domain Validation CA SHA2
Valid From: 9th August, 2021
Valid To: 9th August, 2022
Subject: CN = dttsonline.com
Hash: a1787ca2
Issuer: CN = Certum Domain Validation CA SHA2
OU = Certum Certification Authority
O = Unizeto Technologies S.A.
S = PL
Version: 2
Serial Number: 107290557053860144759493556680424134279
Serial Number (Hex): 50B768DF58C7994B767A23B83CAF9687
Valid From: 9th August, 2024
Valid To: 9th August, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:E5:31:AD:BF:3A:11:96:F4:83:BC:50:3C:D4:B7:90:9B:90:EE:DE:25
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.certum.pl/dvcasha2.crl

Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.2.616.1.113527.2.5.1.3
CPS: https://www.certum.pl/CPS

Authority Information Access: OCSP - URI:http://dvcasha2.ocsp-certum.com
CA Issuers - URI:http://repository.certum.pl/dvcasha2.cer

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Aug 9 08:51:50.072 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:0C:38:7F:9D:41:4C:60:84:73:87:F9:21:
64:BC:BC:13:74:F5:33:7A:2F:EA:48:36:D9:E6:FE:80:
81:33:4D:0E:02:21:00:92:C7:7D:8B:3F:7D:97:B6:52:
F9:0E:F2:FC:D9:77:65:C2:5E:D7:A9:E5:68:CC:ED:A3:
3B:D4:0A:84:34:31:C3
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Aug 9 08:51:50.068 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:F4:88:81:01:16:CE:29:36:F0:64:AF:
05:51:D2:3E:25:6E:53:B3:10:B6:80:F2:02:10:F9:53:
39:96:0F:7A:B2:02:21:00:92:38:29:08:10:C4:F6:A2:
7B:C0:D9:B6:61:66:20:10:6A:F1:36:04:55:CB:B5:9F:
28:78:32:D2:E2:AC:2E:CD
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 55:81:D4:C2:16:90:36:01:4A:EA:0B:9B:57:3C:53:F0:
C0:E4:38:78:70:25:08:17:2F:A3:AA:1D:07:13:D3:0C
Timestamp : Aug 9 08:51:50.110 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:A7:7E:65:06:4E:94:00:C3:E2:B3:3F:
55:66:6C:52:1E:2A:C6:8F:CF:3D:10:28:38:29:5A:2F:
71:60:6E:9D:25:02:21:00:A6:C0:94:90:40:74:AD:E3:
82:CF:7B:9F:90:D3:05:DE:68:E4:88:6F:13:BE:29:47:
58:C9:F6:8A:DB:EC:A9:84
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.dttsonline.com
DNS:dttsonline.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 24th August, 2021
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Set-Cookie: *

Whois Lookup

Created: 11th April, 2014
Changed: 31st March, 2021
Expires: 11th April, 2022
Registrar: TUCOWS, INC.
Status: ok
Nameservers: m.ns.arvancdn.com
q.ns.arvancdn.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: REDACTED FOR PRIVACY
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: AB
Owner Country: CA
Owner Phone: REDACTED FOR PRIVACY
Owner Email: https://tieredaccess.com/contact/e8fc4084-7cd2-4e58-a329-0b5f37ca35e0
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY
Full Whois: Domain Name: DTTSONLINE.COM
Registry Domain ID: 1854371948_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://tucowsdomains.com
Updated Date: 2021-03-31T05:24:22
Creation Date: 2014-04-11T20:57:34
Registrar Registration Expiration Date: 2022-04-11T20:57:34
Registrar: TUCOWS, INC.
Registrar IANA ID: 69
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID:
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: AB
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: CA
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext:
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext:
Registrant Email: https://tieredaccess.com/contact/e8fc4084-7cd2-4e58-a329-0b5f37ca35e0
Registry Admin ID:
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext:
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext:
Admin Email: REDACTED FOR PRIVACY
Registry Tech ID:
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext:
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext:
Tech Email: REDACTED FOR PRIVACY
Name Server: q.ns.arvancdn.com
Name Server: m.ns.arvancdn.com
DNSSEC: unsigned
Registrar Abuse Contact Email: domainabuse@tucows.com
Registrar Abuse Contact Phone: +1.4165350123
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-08-24T03:26:26Z <<<

"For more information on Whois status codes, please visit https://icann.org/epp"

The Data in the Tucows Registrar WHOIS database is provided to you by Tucows
for information purposes only, and may be used to assist you in obtaining
information about or related to a domain name's registration record.

Tucows makes this information available "as is," and does not guarantee its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
a) allow, enable, or otherwise support the transmission by e-mail,
telephone, or facsimile of mass, unsolicited, commercial advertising or
solicitations to entities other than the data recipient's own existing
customers; or (b) enable high volume, automated, electronic processes that
send queries or data to the systems of any Registry Operator or
ICANN-Accredited registrar, except as reasonably necessary to register
domain names or modify existing registrations.

The compilation, repackaging, dissemination or other use of this Data is
expressly prohibited without the prior written consent of Tucows.

Tucows reserves the right to terminate your access to the Tucows WHOIS
database in its sole discretion, including without limitation, for excessive
querying of the WHOIS database or for failure to otherwise abide by this
policy.

Tucows reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by these terms.

NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY. LACK OF A DOMAIN
RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.

Nameservers

Name IP Address
m.ns.arvancdn.com 185.215.234.253
q.ns.arvancdn.com 185.215.235.253
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address