tran.com

tran.com may not be SSL secured

Free website and domain report on tran.com

Last Updated: 28th October, 2021 Update Now
Overview

Snoop Summary for tran.com

This is a free and comprehensive report about tran.com. Tran.com is hosted in Canada on a server with an IP address of 64.99.80.121, where CAD is the local currency and the local language is English. Tran.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If tran.com was to be sold it would possibly be worth $879 USD (based on the daily revenue potential of the website over a 24 month period). Tran.com receives an estimated 418 unique visitors every day - a decent amount of traffic! This report was last updated 28th October, 2021.

About tran.com

Site Preview: tran.com tran.com
Title: RealNames | A more meaningful email address
Description: Get an email address at tran.com. It's ad-free, reliable email that's based on your own name | tran.com
Keywords and Tags: internet services
Related Terms: tran, tran nhat phong
Fav Icon:
Age: Over 26 years old
Domain Created: 4th April, 1997
Domain Updated: 7th March, 2021
Domain Expires: 5th April, 2022
Review

Snoop Score

1/5

Valuation

$879 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,550,327
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: 418
Monthly Visitors: 12,718
Yearly Visitors: 152,509
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $36 USD
Yearly Revenue: $435 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: tran.com 8
Domain Name: tran 4
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

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

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for tran.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.
Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 1.0 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.007
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://tran.com/
http/1.1
0
159.9400001578
4695
8288
200
text/html
Document
http://tran.com/assets/application-388f92fc75d6fb055ce8bfafa846ff05.css
http/1.1
174.11900009029
394.58400011063
27644
147188
200
text/css
Stylesheet
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
http/1.1
174.25599996932
421.36800009757
139653
139322
200
application/javascript
Script
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
http/1.1
174.38400001265
466.4800001774
230284
229953
200
application/javascript
Script
http://tran.com/assets/realnames-d36ce9460d29c8bd560ff32d98a195c1.png
http/1.1
432.52200004645
531.19500004686
26309
25921
200
image/png
Image
http://tran.com/assets/tucows-fca298afc1945c4cd224d734c5dc50ab.png
http/1.1
480.32200010493
690.2340000961
13489
13101
200
image/png
Image
http://tran.com/assets/cc-832f478e96f6d6a43eb15dd70d0ea85f.png
http/1.1
517.19100004993
712.97300001606
122130
121740
200
image/png
Image
http://tran.com/assets/realnames_homepage_woman-726212691ae7a515a2ae33141a572c7a.png
http/1.1
519.68899997883
777.28600008413
348092
347702
200
image/png
Image
http://tran.com/assets/fontawesome-webfont-5675dbc1b506f9840ba6163a640d59ee.woff?v=4.2.0
http/1.1
524.6960001532
587.01699995436
65780
65452
200
application/font-woff
Font
http://tran.com/assets/avenir_light-3ddcda2308f4a0cab5d9422f8ec41976.ttf
http/1.1
524.87500011921
645.26600018144
27479
27148
200
application/octet-stream
Font
http://tran.com/assets/avenir_bold-940fca00bcddbbf4f0dd4842f054b0a5.ttf
http/1.1
525.16199997626
629.49700001627
79444
79112
200
application/octet-stream
Font
http://www.googletagmanager.com/gtm.js?id=GTM-PPHLFT
http/1.1
542.93200001121
566.98000011966
313
0
302
text/html
https://www.googletagmanager.com/gtm.js?id=GTM-PPHLFT
h2
567.82700004987
590.33400006592
42026
112444
200
application/javascript
Script
http://www.google-analytics.com/analytics.js
http/1.1
622.69000010565
627.35199998133
20204
49529
200
text/javascript
Script
http://connect.facebook.net/en_US/fbds.js
http/1.1
625.03200001083
660.55100015365
3103
4024
200
application/x-javascript
Script
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j93&tid=UA-4171338-35&cid=290041046.1635427814&jid=540947435&gjid=782221091&_gid=1155016374.1635427814&_u=YGBAgAABAAAAAE~&z=1631864287
h2
669.61900005117
673.28099999577
678
1
200
text/plain
XHR
https://www.google-analytics.com/j/collect?v=1&_v=j93&a=525068437&t=pageview&_s=1&dl=http%3A%2F%2Ftran.com%2F&ul=en-us&de=UTF-8&dt=RealNames%20%7C%20A%20more%20meaningful%20email%20address&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YGDAAAABAAAAAG~&jid=2124705753&gjid=1761690057&cid=290041046.1635427814&tid=UA-4171338-10&_gid=1155016374.1635427814&_r=1&gtm=2wgar0PPHLFT&z=91300646
h2
679.4420001097
683.00900002941
605
1
200
text/plain
XHR
http://www.google-analytics.com/collect?v=1&_v=j93&a=525068437&t=pageview&_s=1&dl=http%3A%2F%2Ftran.com%2F&ul=en-us&de=UTF-8&dt=RealNames%20%7C%20A%20more%20meaningful%20email%20address&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YGBAgAAB~&jid=540947435&gjid=782221091&cid=290041046.1635427814&tid=UA-4171338-35&_gid=1155016374.1635427814&gtm=2wgar0PPHLFT&z=1852341718
http/1.1
680.26200006716
683.76200017519
429
35
200
image/gif
Image
https://www.facebook.com/tr/?id=null&ev=6024222745998&dl=http%3A%2F%2Ftran.com%2F&rl=&if=false&ts=1635427814275&cd[value]=0.00&cd[currency]=USD
h2
694.80499997735
710.24399995804
648
44
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
194.581
8.639
427.745
8.1
463.951
29.304
511.741
37.805
549.559
23.158
572.779
22.111
633.635
10.871
644.976
11.943
663.8
5.814
669.938
42.153
716.027
6.061
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 138 KiB
Images can slow down the page's load time. Tran.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://tran.com/assets/cc-832f478e96f6d6a43eb15dd70d0ea85f.png
121740
116612
http://tran.com/assets/realnames-d36ce9460d29c8bd560ff32d98a195c1.png
25921
19441
http://tran.com/assets/tucows-fca298afc1945c4cd224d734c5dc50ab.png
13101
5628
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Tran.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Tran.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Tran.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 25 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Tran.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://tran.com/assets/application-388f92fc75d6fb055ce8bfafa846ff05.css
27644
25610
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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 160 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://tran.com/
160.933
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Tran.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Tran.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
235
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 1,126 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://tran.com/assets/realnames_homepage_woman-726212691ae7a515a2ae33141a572c7a.png
348092
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
230284
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
139653
http://tran.com/assets/cc-832f478e96f6d6a43eb15dd70d0ea85f.png
122130
http://tran.com/assets/avenir_bold-940fca00bcddbbf4f0dd4842f054b0a5.ttf
79444
http://tran.com/assets/fontawesome-webfont-5675dbc1b506f9840ba6163a640d59ee.woff?v=4.2.0
65780
https://www.googletagmanager.com/gtm.js?id=GTM-PPHLFT
42026
http://tran.com/assets/application-388f92fc75d6fb055ce8bfafa846ff05.css
27644
http://tran.com/assets/avenir_light-3ddcda2308f4a0cab5d9422f8ec41976.ttf
27479
http://tran.com/assets/realnames-d36ce9460d29c8bd560ff32d98a195c1.png
26309
Avoids an excessive DOM size — 71 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
71
Maximum DOM Depth
11
Maximum Child Elements
7
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. Tran.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)
http://tran.com/
62.334
3.86
1.436
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
53.53
40.91
3.921
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)
Script Evaluation
138.128
Other
44.973
Style & Layout
37.805
Parse HTML & CSS
13.276
Rendering
12.263
Script Parsing & Compilation
12.251
Keep request counts low and transfer sizes small — 19 requests • 1,126 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
19
1153005
Image
6
511097
Script
5
435270
Font
3
172703
Stylesheet
1
27644
Document
1
4695
Other
3
1596
Media
0
0
Third-party
8
68006
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)
42339
0
21238
0
3751
0
678
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0023975148632474
0.0017292348005534
0.0014620487796014
0.00084729183300167
0.00022337094999199
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of tran.com on mobile screens.

Budgets

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

Metrics

Largest Contentful Paint — 1.8 s
The timing of the largest text or image that is painted.

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 580 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Tran.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://tran.com/assets/application-388f92fc75d6fb055ce8bfafa846ff05.css
27644
110
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
139653
350
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
230284
430
Reduce unused JavaScript — Potential savings of 274 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
230284
148050
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
139653
83688
http://www.googletagmanager.com/gtm.js?id=GTM-PPHLFT
112444
49023
Serve images in next-gen formats — Potential savings of 350 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://tran.com/assets/realnames_homepage_woman-726212691ae7a515a2ae33141a572c7a.png
347702
220828.1
http://tran.com/assets/cc-832f478e96f6d6a43eb15dd70d0ea85f.png
121740
104467.1
http://tran.com/assets/realnames-d36ce9460d29c8bd560ff32d98a195c1.png
25921
22493.05
http://tran.com/assets/tucows-fca298afc1945c4cd224d734c5dc50ab.png
13101
10313.15
Enable text compression — Potential savings of 250 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
229953
164105
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
139322
92143

Diagnostics

Serve static assets with an efficient cache policy — 12 resources found
Tran.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://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
0
230284
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
0
139653
http://tran.com/assets/avenir_bold-940fca00bcddbbf4f0dd4842f054b0a5.ttf
0
79444
http://tran.com/assets/fontawesome-webfont-5675dbc1b506f9840ba6163a640d59ee.woff?v=4.2.0
0
65780
http://tran.com/assets/application-388f92fc75d6fb055ce8bfafa846ff05.css
0
27644
http://tran.com/assets/avenir_light-3ddcda2308f4a0cab5d9422f8ec41976.ttf
0
27479
http://connect.facebook.net/en_US/fbds.js
1200000
3103
http://www.google-analytics.com/analytics.js
7200000
20204
http://tran.com/assets/realnames_homepage_woman-726212691ae7a515a2ae33141a572c7a.png
2592000000
348092
http://tran.com/assets/cc-832f478e96f6d6a43eb15dd70d0ea85f.png
2592000000
122130
http://tran.com/assets/realnames-d36ce9460d29c8bd560ff32d98a195c1.png
2592000000
26309
http://tran.com/assets/tucows-fca298afc1945c4cd224d734c5dc50ab.png
2592000000
13489
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://tran.com/assets/fontawesome-webfont-5675dbc1b506f9840ba6163a640d59ee.woff?v=4.2.0
62.320999801159
http://tran.com/assets/avenir_light-3ddcda2308f4a0cab5d9422f8ec41976.ttf
120.39100006223
http://tran.com/assets/avenir_bold-940fca00bcddbbf4f0dd4842f054b0a5.ttf
104.33500004001
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://tran.com/assets/cc-832f478e96f6d6a43eb15dd70d0ea85f.png
Cc
http://tran.com/assets/tucows-fca298afc1945c4cd224d734c5dc50ab.png
70

Accessibility

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

Tables and lists

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

Names and labels

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

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

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Contrast

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

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that tran.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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.11.2
React
15.4.1
Moment.js
2.9.0
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 — 15 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://tran.com/
Allowed
http://tran.com/assets/application-388f92fc75d6fb055ce8bfafa846ff05.css
Allowed
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
Allowed
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
Allowed
http://tran.com/assets/realnames-d36ce9460d29c8bd560ff32d98a195c1.png
Allowed
http://tran.com/assets/tucows-fca298afc1945c4cd224d734c5dc50ab.png
Allowed
http://tran.com/assets/cc-832f478e96f6d6a43eb15dd70d0ea85f.png
Allowed
http://tran.com/assets/realnames_homepage_woman-726212691ae7a515a2ae33141a572c7a.png
Allowed
http://tran.com/assets/fontawesome-webfont-5675dbc1b506f9840ba6163a640d59ee.woff?v=4.2.0
Allowed
http://tran.com/assets/avenir_light-3ddcda2308f4a0cab5d9422f8ec41976.ttf
Allowed
http://tran.com/assets/avenir_bold-940fca00bcddbbf4f0dd4842f054b0a5.ttf
Allowed
http://www.googletagmanager.com/gtm.js?id=GTM-PPHLFT
Allowed
http://www.google-analytics.com/analytics.js
Allowed
http://connect.facebook.net/en_US/fbds.js
Allowed
http://www.google-analytics.com/collect?v=1&_v=j93&a=525068437&t=pageview&_s=1&dl=http%3A%2F%2Ftran.com%2F&ul=en-us&de=UTF-8&dt=RealNames%20%7C%20A%20more%20meaningful%20email%20address&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YGBAgAAB~&jid=540947435&gjid=782221091&cid=290041046.1635427814&tid=UA-4171338-35&_gid=1155016374.1635427814&gtm=2wgar0PPHLFT&z=1852341718
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 7 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
4
Medium
3
Medium
100

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

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

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of tran.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 tran.com on mobile screens.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 72
Performance 75
Accessibility 78
Best Practices 80
SEO 100
Progressive Web App 25
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
75

Performance

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

Metrics

Speed Index — 3.2 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 10 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 70 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://tran.com/
http/1.1
0
107.53299994394
4681
8288
200
text/html
Document
http://tran.com/assets/application-388f92fc75d6fb055ce8bfafa846ff05.css
http/1.1
117.92099988088
249.96599997394
27651
147188
200
text/css
Stylesheet
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
http/1.1
118.19799989462
300.77699990943
139653
139322
200
application/javascript
Script
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
http/1.1
118.50599991158
325.38000005297
230284
229953
200
application/javascript
Script
http://tran.com/assets/realnames-d36ce9460d29c8bd560ff32d98a195c1.png
http/1.1
309.53299999237
361.07000010088
26309
25921
200
image/png
Image
http://tran.com/assets/tucows-fca298afc1945c4cd224d734c5dc50ab.png
http/1.1
341.36900003068
500.10400009342
13489
13101
200
image/png
Image
http://tran.com/assets/cc-832f478e96f6d6a43eb15dd70d0ea85f.png
http/1.1
376.0309999343
569.91899991408
122130
121740
200
image/png
Image
http://tran.com/assets/fontawesome-webfont-5675dbc1b506f9840ba6163a640d59ee.woff?v=4.2.0
http/1.1
384.17400000617
445.08600002155
65780
65452
200
application/font-woff
Font
http://tran.com/assets/avenir_light-3ddcda2308f4a0cab5d9422f8ec41976.ttf
http/1.1
384.59799997509
433.3349999506
27479
27148
200
application/octet-stream
Font
http://tran.com/assets/avenir_bold-940fca00bcddbbf4f0dd4842f054b0a5.ttf
http/1.1
385.42499998584
455.32299997285
79444
79112
200
application/octet-stream
Font
http://www.googletagmanager.com/gtm.js?id=GTM-PPHLFT
http/1.1
399.27599998191
420.43900000863
326
0
302
text/html
https://www.googletagmanager.com/gtm.js?id=GTM-PPHLFT
h2
421.57900007442
430.74199999683
41991
112444
200
application/javascript
Script
http://www.google-analytics.com/analytics.js
http/1.1
459.71399988048
463.18700001575
20204
49529
200
text/javascript
Script
http://connect.facebook.net/en_US/fbds.js
http/1.1
461.33599989116
471.7220000457
3103
4024
200
application/x-javascript
Script
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j93&tid=UA-4171338-35&cid=49950931.1635427830&jid=147754997&gjid=1998990108&_gid=185461814.1635427830&_u=YGBAgAABAAAAAE~&z=1487888462
h2
489.29199995473
492.63500003144
678
1
200
text/plain
XHR
https://www.google-analytics.com/j/collect?v=1&_v=j93&a=1900562161&t=pageview&_s=1&dl=http%3A%2F%2Ftran.com%2F&ul=en-us&de=UTF-8&dt=RealNames%20%7C%20A%20more%20meaningful%20email%20address&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YGDAAAABAAAAAG~&jid=1854521469&gjid=730682776&cid=49950931.1635427830&tid=UA-4171338-10&_gid=185461814.1635427830&_r=1&gtm=2wgar0PPHLFT&z=1910620144
h2
498.39699990116
504.63999994099
605
1
200
text/plain
XHR
http://www.google-analytics.com/collect?v=1&_v=j93&a=1900562161&t=pageview&_s=1&dl=http%3A%2F%2Ftran.com%2F&ul=en-us&de=UTF-8&dt=RealNames%20%7C%20A%20more%20meaningful%20email%20address&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YGBAgAAB~&jid=147754997&gjid=1998990108&cid=49950931.1635427830&tid=UA-4171338-35&_gid=185461814.1635427830&gtm=2wgar0PPHLFT&z=1911321258
http/1.1
499.00400009938
502.50399997458
429
35
200
image/gif
Image
https://www.facebook.com/tr/?id=null&ev=6024222745998&dl=http%3A%2F%2Ftran.com%2F&rl=&if=false&ts=1635427829846&cd[value]=0.00&cd[currency]=USD
h2
505.48799987882
516.59199991263
648
44
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
138.559
6.065
280.094
6.773
338.048
20.933
369.949
35.566
405.526
19.509
426.446
21.029
469.291
8.099
479.651
10.681
498.153
29.729
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
Images can slow down the page's load time. Tran.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Tran.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Tran.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Tran.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 25 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Tran.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://tran.com/assets/application-388f92fc75d6fb055ce8bfafa846ff05.css
27651
25400
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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 110 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://tran.com/
108.527
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Tran.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Tran.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
235
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 786 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
230284
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
139653
http://tran.com/assets/cc-832f478e96f6d6a43eb15dd70d0ea85f.png
122130
http://tran.com/assets/avenir_bold-940fca00bcddbbf4f0dd4842f054b0a5.ttf
79444
http://tran.com/assets/fontawesome-webfont-5675dbc1b506f9840ba6163a640d59ee.woff?v=4.2.0
65780
https://www.googletagmanager.com/gtm.js?id=GTM-PPHLFT
41991
http://tran.com/assets/application-388f92fc75d6fb055ce8bfafa846ff05.css
27651
http://tran.com/assets/avenir_light-3ddcda2308f4a0cab5d9422f8ec41976.ttf
27479
http://tran.com/assets/realnames-d36ce9460d29c8bd560ff32d98a195c1.png
26309
http://www.google-analytics.com/analytics.js
20204
Avoids an excessive DOM size — 71 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
71
Maximum DOM Depth
11
Maximum Child Elements
7
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. Tran.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://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
196.248
156.712
14.604
http://tran.com/
160.764
13.148
4.54
http://www.google-analytics.com/analytics.js
127.696
109.912
3.608
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
101.328
80.764
10.644
Unattributable
88.632
10.212
0.896
http://www.googletagmanager.com/gtm.js?id=GTM-PPHLFT
78.436
66.728
8.132
Minimizes main-thread work — 0.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
443.248
Other
127.212
Style & Layout
110.34
Parse HTML & CSS
45.28
Script Parsing & Compilation
43.116
Rendering
18.056
Keep request counts low and transfer sizes small — 18 requests • 786 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
18
804884
Script
5
435235
Font
3
172703
Image
5
163005
Stylesheet
1
27651
Document
1
4681
Other
3
1609
Media
0
0
Third-party
8
67984
Minimize third-party usage — Third-party code blocked the main thread for 50 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)
21238
53.192
42317
0
3751
0
678
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
8.0143292744954E-5
3.4044053819444E-5
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)
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
1740
84
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
3120
71
http://www.google-analytics.com/analytics.js
4868
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.
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 tran.com on mobile screens.

Budgets

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

Metrics

Time to Interactive — 4.9 s
The time taken for the page to become fully interactive.

Other

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

Opportunities

Serve images in next-gen formats — Potential savings of 134 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://tran.com/assets/cc-832f478e96f6d6a43eb15dd70d0ea85f.png
121740
104467.1
http://tran.com/assets/realnames-d36ce9460d29c8bd560ff32d98a195c1.png
25921
22493.05
http://tran.com/assets/tucows-fca298afc1945c4cd224d734c5dc50ab.png
13101
10313.15

Metrics

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

Opportunities

Eliminate render-blocking resources — Potential savings of 2,510 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Tran.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://tran.com/assets/application-388f92fc75d6fb055ce8bfafa846ff05.css
27651
480
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
139653
1830
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
230284
2430
Reduce unused JavaScript — Potential savings of 274 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
230284
148050
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
139653
83688
http://www.googletagmanager.com/gtm.js?id=GTM-PPHLFT
112444
49023
Enable text compression — Potential savings of 250 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
229953
164105
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
139322
92143

Diagnostics

Serve static assets with an efficient cache policy — 11 resources found
Tran.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://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
0
230284
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
0
139653
http://tran.com/assets/avenir_bold-940fca00bcddbbf4f0dd4842f054b0a5.ttf
0
79444
http://tran.com/assets/fontawesome-webfont-5675dbc1b506f9840ba6163a640d59ee.woff?v=4.2.0
0
65780
http://tran.com/assets/application-388f92fc75d6fb055ce8bfafa846ff05.css
0
27651
http://tran.com/assets/avenir_light-3ddcda2308f4a0cab5d9422f8ec41976.ttf
0
27479
http://connect.facebook.net/en_US/fbds.js
1200000
3103
http://www.google-analytics.com/analytics.js
7200000
20204
http://tran.com/assets/cc-832f478e96f6d6a43eb15dd70d0ea85f.png
2592000000
122130
http://tran.com/assets/realnames-d36ce9460d29c8bd560ff32d98a195c1.png
2592000000
26309
http://tran.com/assets/tucows-fca298afc1945c4cd224d734c5dc50ab.png
2592000000
13489
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://tran.com/assets/fontawesome-webfont-5675dbc1b506f9840ba6163a640d59ee.woff?v=4.2.0
60.912000015378
http://tran.com/assets/avenir_light-3ddcda2308f4a0cab5d9422f8ec41976.ttf
48.736999975517
http://tran.com/assets/avenir_bold-940fca00bcddbbf4f0dd4842f054b0a5.ttf
69.897999987006

Other

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

Accessibility

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

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.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[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.

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

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that tran.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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.11.2
React
15.4.1
Moment.js
2.9.0
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 — 14 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://tran.com/
Allowed
http://tran.com/assets/application-388f92fc75d6fb055ce8bfafa846ff05.css
Allowed
http://tran.com/assets/application-3d05dab7414753418b0c10a83e32ec2b.js
Allowed
http://tran.com/assets/main-284327f85aa798d6f36235562f85f83b.js
Allowed
http://tran.com/assets/realnames-d36ce9460d29c8bd560ff32d98a195c1.png
Allowed
http://tran.com/assets/tucows-fca298afc1945c4cd224d734c5dc50ab.png
Allowed
http://tran.com/assets/cc-832f478e96f6d6a43eb15dd70d0ea85f.png
Allowed
http://tran.com/assets/fontawesome-webfont-5675dbc1b506f9840ba6163a640d59ee.woff?v=4.2.0
Allowed
http://tran.com/assets/avenir_light-3ddcda2308f4a0cab5d9422f8ec41976.ttf
Allowed
http://tran.com/assets/avenir_bold-940fca00bcddbbf4f0dd4842f054b0a5.ttf
Allowed
http://www.googletagmanager.com/gtm.js?id=GTM-PPHLFT
Allowed
http://www.google-analytics.com/analytics.js
Allowed
http://connect.facebook.net/en_US/fbds.js
Allowed
http://www.google-analytics.com/collect?v=1&_v=j93&a=1900562161&t=pageview&_s=1&dl=http%3A%2F%2Ftran.com%2F&ul=en-us&de=UTF-8&dt=RealNames%20%7C%20A%20more%20meaningful%20email%20address&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YGBAgAAB~&jid=147754997&gjid=1998990108&cid=49950931.1635427830&tid=UA-4171338-35&_gid=185461814.1635427830&gtm=2wgar0PPHLFT&z=1911321258
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 7 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
4
Medium
3
Medium
100

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

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

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of tran.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 tran.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: 64.99.80.121
Continent: North America
Country: Canada
Canada Flag
Region:
City:
Longitude: -79.3716
Latitude: 43.6319
Currencies: CAD
Languages: English
French

Web Hosting Provider

Name IP Address
Tucows.com Co.
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

Technical

DNS Lookup

A Records

Host IP Address Class TTL
tran.com. 64.99.80.121 IN 300

NS Records

Host Nameserver Class TTL
tran.com. ns1.mdnsservice.com. IN 300
tran.com. ns1.mailbank.com. IN 300
tran.com. ns2.mdnsservice.com. IN 300
tran.com. ns3.mdnsservice.com. IN 300
tran.com. ns2.mailbank.com. IN 300

MX Records

Priority Host Server Class TTL
10 tran.com. mx.netidentity.com.cust.hostedemail.com. IN 300
20 tran.com. mx.netidentity.com.cust.hostedemail.com. IN 300

SOA Records

Domain Name Primary NS Responsible Email TTL
tran.com. ns1.mdnsservice.com. hostmaster.mdnsservice.com. 300

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx/1.6.2
Date: 28th October, 2021
Content-Type: text/html; charset=utf-8
Cache-Control: max-age=0, private, must-revalidate
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
ETag: W/"2fd4f00403f1f7d622f7096b15449cf1"
X-Request-Id: 5076e989-38df-4436-a859-5df8faf09ae6
X-Runtime: 0.012056
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"

Whois Lookup

Created: 4th April, 1997
Changed: 7th March, 2021
Expires: 5th April, 2022
Registrar: TUCOWS, INC.
Status: clientTransferProhibited
clientUpdateProhibited
Nameservers: ns1.mailbank.com
ns2.mailbank.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: ON
Owner Country: CA
Owner Phone: REDACTED FOR PRIVACY
Owner Email: https://tieredaccess.com/contact/b2d47f2b-05f1-4342-94fb-2c47221b39df
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: TRAN.COM
Registry Domain ID: 2156738_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://tucowsdomains.com
Updated Date: 2021-03-07T05:27:58
Creation Date: 1997-04-04T05:00:00
Registrar Registration Expiration Date: 2022-04-05T04:00:00
Registrar: TUCOWS, INC.
Registrar IANA ID: 69
Reseller: Tucows.com Co.
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
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: ON
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/b2d47f2b-05f1-4342-94fb-2c47221b39df
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: ns1.mailbank.com
Name Server: ns2.mailbank.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-10-28T13:30:10Z <<<

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

Registration Service Provider:
Tucows.com Co., pninquiry@tucows.com
http://www.tucowsinc.com
This domain name is part of RealNames and is one of the Tucows owned
portfolio of shared domain names. The business concept behind these
domains is to allow multiple users to share domain names that
correspond either with their personal names (surnames) or their
personal interests.

Get your own personal email and web address at
Hover (http://www.hover.com). If you have any questions about this
domain name, please email pninquiry@tucows.com.

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
ns1.mailbank.com 216.40.47.18
ns2.mailbank.com 64.98.148.11
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5
0/5