Tsetmc - Tsetmc.com

Overview

Snoop Summary for tsetmc.com

This is a free and comprehensive report about tsetmc.com. Tsetmc.com is expected to earn an estimated $45,885 USD per day from advertising revenue. The sale of tsetmc.com would possibly be worth $33,495,761 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Tsetmc.com receives an estimated 4,928,067 unique visitors every day - an unbelievable amount of traffic! This report was last updated 30th November, 2022.

About tsetmc.com

Site Preview:
Title:
Description:
Keywords and Tags:	business, tsetmc, بورس, بورس اوراق بهادار, بورس تهران, خاور, خساپا, خودرو, خپارس, دیده بان بازار, ذوب, سمگا, شپلی, فاراک, لکما, وتجارت
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:

Review

Snoop Score

4/5 (Excellent!)

Valuation

$33,495,761 USD

Note: All valuation figures are estimates.

Popularity

Worldwide Sensation

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	511
Alexa Reach:	0.0835%
SEMrush Rank (US):	28,401
SEMrush Authority Score:	65
Moz Domain Authority:	34
Moz Page Authority:	46

Rank By Country

Country	Alexa Rank
Germany	1,990
France	2,190
Iran, Islamic Republic Of	7
United States	3,402

Show Rank By Country

Organic vs Paid (Google Ads)

	Organic	Paid
Keywords:	5,359	0
Traffic:	84,014	0
Cost:	$1,796 USD	$0 USD

Traffic

Visitors

Daily Visitors:	4,928,067
Monthly Visitors:	149,994,836
Yearly Visitors:	1,798,744,455

Note: All visitors figures are estimates.

Visitors By Country

Country	Visitors (Unique)	Percentage
Germany	Daily: 39,425 Monthly: 1,199,959 Yearly: 14,389,956	0.8%
France	Daily: 24,640 Monthly: 749,974 Yearly: 8,993,722	0.5%
Iran, Islamic Republic Of	Daily: 4,642,239 Monthly: 141,295,135 Yearly: 1,694,417,277	94.2%
Other	Daily: 108,417 Monthly: 3,299,886 Yearly: 39,572,378	2.2%
United States	Daily: 113,346 Monthly: 3,449,881 Yearly: 41,371,122	2.3%

Note: All visitors figures are estimates.

Revenue

Daily Revenue:	$45,885 USD
Monthly Revenue:	$1,396,582 USD
Yearly Revenue:	$16,747,876 USD

Note: All revenue figures are estimates.

Revenue By Country

Country	Revenue	Percentage
Germany	Daily: $1,842 USD Monthly: $56,068 USD Yearly: $672,367 USD	4%
France	Daily: $638 USD Monthly: $19,411 USD Yearly: $232,780 USD	1.4%
Iran, Islamic Republic Of	Daily: $0 USD Monthly: $0 USD Yearly: $0 USD	<0.1%
Other	Daily: $0 USD Monthly: $0 USD Yearly: $0 USD	<0.1%
United States	Daily: $43,405 USD Monthly: $1,321,103 USD Yearly: $15,842,729 USD	94.6%

Note: All revenue figures are estimates.

SEO

Backlinks Analysis (SEMrush)

Backlinks:	4,089,250
Referring Domains:	2,473
Referring IPs:	1,734

Tsetmc.com has 4,089,250 backlinks according to SEMrush. 53% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve tsetmc.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.

100% of tsetmc.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top Ranking Keywords (US)

1

Keyword: بورس

Ranked Page: http://www.tsetmc.com/

2

Keyword: tsetmc

Ranked Page: http://en.tsetmc.com/

3

Keyword: بورس تهران

Ranked Page: http://www.tsetmc.com/

4

Keyword: وتجارت

Ranked Page: http://www.tsetmc.com/loader.aspx?ParTree=151311&i=63917421733088077

5

Keyword: ذوب

Ranked Page: http://www.tsetmc.com/loader.aspx?ParTree=151311&i=9211775239375291

Domain Analysis

	Value	Length
Domain:	tsetmc.com	10
Domain Name:	tsetmc	6
Extension (TLD):	com	3

Page Speed Analysis

Average Load Time:	1.54 seconds
Load Time Comparison:	Faster than 59% of sites

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: http://tsetmc.com/Loader.aspx?ParTree=15

Updated: 8th May, 2020

2.88 seconds

First Contentful Paint (FCP)

30%

46%

24%

0.08 seconds

First Input Delay (FID)

95%

2%

3%

Simulate loading on desktop

Performance

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

Metrics

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

Other

Total Blocking Time — 50 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).

Network Requests
Below is a list of network requests that were made during page load.

URL	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://tsetmc.com/	0	718.59499998391	428	0	302	text/html
http://tsetmc.com/Loader.aspx?ParTree=15	719.09100003541	1646.8150001019	26023	244061	200	text/html	Document
https://www.googletagmanager.com/gtag/js?id=UA-63076930-1	1671.5940004215	1696.0730003193	31177	82446	200	application/javascript	Script
http://tsetmc.com/tsev2/res/loader.aspx?t=j&_469	1677.0570003428	2862.7190003172	135735	527953	200	text/javascript	XHR
http://www.googleapis.com/	2930.9249999933	2941.2960000336	700	0	404	text/html	XHR
http://tsetmc.com/tsev2/res/loader.aspx?t=s&_469	2932.57800024	3895.8820002154	35722	66372	200	text/css	XHR
	3930.9090003371	3930.9900002554	0	1807	200	image/png	Image
	3931.3610000536	3931.4120002091	0	1204	200	image/png	Image
	3931.6650000401	3931.7040001042	0	452	200	image/png	Image
	3931.8740000017	3931.9090000354	0	397	200	image/png	Image
	3932.0650002919	3932.0970000699	0	482	200	image/png	Image
	3932.2700002231	3932.3030002415	0	355	200	image/png	Image
	3932.4570000172	3932.5640001334	0	610	200	image/png	Image
	3932.8200002201	3932.9130002297	0	1875	200	image/png	Image
https://www.google-analytics.com/analytics.js	4308.273000177	4313.7320000678	19076	45892	200	text/javascript	Script
https://www.google-analytics.com/r/collect?v=1&_v=j82&a=381218561&t=pageview&_s=1&dl=http%3A%2F%2Ftsetmc.com%2FLoader.aspx%3FParTree%3D15&ul=en-us&de=UTF-8&dt=.%3ATSETMC%3A.%20%3A%3A%20%D8%B4%D8%B1%DA%A9%D8%AA%20%D9%85%D8%AF%DB%8C%D8%B1%DB%8C%D8%AA%20%D9%81%D9%86%D8%A7%D9%88%D8%B1%DB%8C%20%D8%A8%D9%88%D8%B1%D8%B3%20%D8%AA%D9%87%D8%B1%D8%A7%D9%86&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUAB~&jid=692359816&gjid=1058217985&cid=1844271441.1588976145&tid=UA-63076930-1&_gid=2067181311.1588976145&_r=1&gtm=2ou4t0&z=845829824	4364.4390003756	4370.7080003805	603	35	200	image/gif	Image

Show Details

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)
1687.395	13.754
1707.353	2231.821
3943.938	5.14
3949.276	11.23
3966.144	17.914
3984.614	5.56
3992.673	21.242
4014.117	7.632
4021.834	298.674
4320.961	9.194
4330.493	12.632
4356.57	44.651

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Tsetmc.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

Properly size images
Images can slow down the page's load time. Tsetmc.com should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Tsetmc.com should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Tsetmc.com should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Tsetmc.com should consider minifying JS files.

Remove unused CSS — Potential savings of 10 KB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Tsetmc.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

URL	Size (Bytes)	Potential Savings (Bytes)
input{font-family:Tahoma} ...	13274	10445

Show Details

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Tsetmc.com should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
(Start) http://tsetmc.com/	0
http://tsetmc.com/Loader.aspx?ParTree=15	190

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Tsetmc.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.

Diagnostics

Avoids enormous network payloads — Total size was 244 KB
Large network payloads can cost users money and are linked to long load times.

URL	Size (Bytes)
http://tsetmc.com/tsev2/res/loader.aspx?t=j&_469	135735
http://tsetmc.com/tsev2/res/loader.aspx?t=s&_469	35722
https://www.googletagmanager.com/gtag/js?id=UA-63076930-1	31177
http://tsetmc.com/Loader.aspx?ParTree=15	26023
https://www.google-analytics.com/analytics.js	19076
http://www.googleapis.com/	700
https://www.google-analytics.com/r/collect?v=1&_v=j82&a=381218561&t=pageview&_s=1&dl=http%3A%2F%2Ftsetmc.com%2FLoader.aspx%3FParTree%3D15&ul=en-us&de=UTF-8&dt=.%3ATSETMC%3A.%20%3A%3A%20%D8%B4%D8%B1%DA%A9%D8%AA%20%D9%85%D8%AF%DB%8C%D8%B1%DB%8C%D8%AA%20%D9%81%D9%86%D8%A7%D9%88%D8%B1%DB%8C%20%D8%A8%D9%88%D8%B1%D8%B3%20%D8%AA%D9%87%D8%B1%D8%A7%D9%86&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUAB~&jid=692359816&gjid=1058217985&cid=1844271441.1588976145&tid=UA-63076930-1&_gid=2067181311.1588976145&_r=1&gtm=2ou4t0&z=845829824	603
http://tsetmc.com/	428

Show Details

Uses efficient cache policy on static assets — 1 resource found
Tsetmc.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)	Size (Bytes)
https://www.google-analytics.com/analytics.js	7200000	19076

Show Details

Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Tsetmc.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.

All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

Keep request counts low and transfer sizes small — 16 requests • 244 KB
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	16	249464
Other	4	172585
Script	2	50253
Document	1	26023
Image	9	603
Stylesheet	0	0
Media	0	0
Font	0	0
Third-party	12	51556

Show Details

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	Size (Bytes)	Main-Thread Blocking Time (Ms)
SHOW DETAILS	31177	0
SHOW DETAILS	19679	0

Show Details

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.

Metrics

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

First CPU Idle — 2.7 s
The time taken for the page's main thread to be quiet enough to handle input.

Diagnostics

Reduce JavaScript execution time — 2.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://tsetmc.com/Loader.aspx?ParTree=15	2233.042	2189.916	37.275
Other	412.145	221.591	1.269

Show Details

Minimize main-thread work — 2.7 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	2472.445
Other	69.177
Style & Layout	64.137
Parse HTML & CSS	48.136
Script Parsing & Compilation	43.832
Rendering	12.967
Garbage Collection	0.719

Show Details

Metrics

First Contentful Paint — 2.7 s
The time taken for the first image or text on the page to be rendered.

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

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

Other

Estimated Input Latency — 710 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive tsetmc.com as laggy when the latency is higher than 0.05 seconds.

Opportunities

Reduce server response times (TTFB) — Root document took 930 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.

Diagnostics

Avoid an excessive DOM size — 4,022 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		4,022
Maximum DOM Depth	SHOW DETAILS	17
Maximum Child Elements	SHOW DETAILS	13

Show Details

Accessibility

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

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`[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-*]` 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.

Audio and video

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

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

`<video>` elements contain a `<track>` element with `[kind="description"]`
Tsetmc.com may provide relevant information that dialogue cannot, by using audio descriptions.

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.

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` 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.

Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.

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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.

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.

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.

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

Show Details

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
فرابورس ایران
شبکه کدال
(2647.54)
(2242.78)
(2647.54)
(0.27)
(752.00)
(0.29)
(2242.78)
(0.72)
(1540.81)
(0.75)
(1051.25)
(0.08)
2999.10
0.42
(25826.51)
(1.27)
(3229.43)
1355.82
1252.3
(945.6)
855.35
757.39
(749.77)
3.09
(0.62)
0.66
3.72
(5)
(5)
3.54
4.99
4.99
(15.92)
4.42
1.48
8.21
9.99
3.77
5.09
3.63
1.5
(2.09)
(1.67)
(22.85)
21.48
(14.75)
13.47
12.57
(10.03)
(9.95)

Show Details

Internationalization and localization

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

Failing Elements
html

Show Details

Names and labels

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.

Failing Elements
a
a
a
a
a
a
a

Show Details

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.

Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.

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.

Best Practices

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

Passing (9)
Failing (5)

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.

Name	Version
jQuery	2.0.2
jQuery (Fast path)

Show Details

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.

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.

Other

Does not use HTTPS — 5 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
http://tsetmc.com/
http://tsetmc.com/Loader.aspx?ParTree=15
http://tsetmc.com/tsev2/res/loader.aspx?t=j&_469
http://www.googleapis.com/
http://tsetmc.com/tsev2/res/loader.aspx?t=s&_469

Show Details

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

URL	Location
http://tsetmc.com/Loader.aspx?ParTree=15	line: 0

Show Details

Includes front-end JavaScript libraries with known security vulnerabilities — 2 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Library Version	Vulnerability Count	Highest Severity
SHOW DETAILS	2	Medium

Show Details

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.

Deprecation / Warning	URL	Line
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.	http://tsetmc.com/Loader.aspx?ParTree=15	0

Show Details

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

URL	Description
http://www.googleapis.com/	Failed to load resource: the server responded with a status of 404 (Not Found)

Show Details

SEO

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

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.

Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.

Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

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.

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

Fast and reliable

Page load is not fast enough on mobile networks — Interactive on simulated mobile network at 11.0 s
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.

`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 5 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
http://tsetmc.com/
http://tsetmc.com/Loader.aspx?ParTree=15
http://tsetmc.com/tsev2/res/loader.aspx?t=j&_469
http://www.googleapis.com/
http://tsetmc.com/tsev2/res/loader.aspx?t=s&_469

Show Details

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.

Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

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

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)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: http://tsetmc.com/Loader.aspx?ParTree=15

Updated: 8th May, 2020

3.49 seconds

First Contentful Paint (FCP)

19%

51%

30%

0.54 seconds

First Input Delay (FID)

2%

85%

13%

Simulate loading on mobile

Performance

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

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive tsetmc.com as laggy when the latency is higher than 0.05 seconds.

Total Blocking Time — 190 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Network Requests
Below is a list of network requests that were made during page load.

URL	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://tsetmc.com/	0	239.47799997404	416	0	302	text/html
http://tsetmc.com/Loader.aspx?ParTree=15	239.85299980268	1194.455999881	84541	1028372	200	text/html	Document
https://www.googletagmanager.com/gtag/js?id=UA-63076930-1	1208.6789999157	1226.0170001537	31177	82446	200	application/javascript	Script
http://tsetmc.com/tsev2/res/loader.aspx?t=j&_469	1211.8899999186	1905.9330001473	135735	527953	200	text/javascript	XHR
http://www.googleapis.com/	1963.1320000626	1972.3709998652	700	0	404	text/html	XHR
http://tsetmc.com/tsev2/res/loader.aspx?t=s&_469	1964.2750001512	2210.1250002161	35677	66372	200	text/css	XHR
	2234.6129999496	2234.6839997917	0	1807	200	image/png	Image
	2234.9299998023	2234.9689998664	0	1204	200	image/png	Image
	2235.0920001045	2235.1150000468	0	452	200	image/png	Image
	2235.2350000292	2235.259000212	0	397	200	image/png	Image
	2235.3509999812	2235.3730001487	0	482	200	image/png	Image
	2235.4689999484	2235.4939999059	0	355	200	image/png	Image
	2235.6110000983	2235.6420001015	0	610	200	image/png	Image
	2235.8129997738	2235.8519998379	0	1875	200	image/png	Image
https://www.google-analytics.com/analytics.js	2288.2679998875	2292.6819999702	19076	45892	200	text/javascript	Script
https://www.google-analytics.com/r/collect?v=1&_v=j82&a=450404267&t=pageview&_s=1&dl=http%3A%2F%2Ftsetmc.com%2FLoader.aspx%3FParTree%3D15&ul=en-us&de=UTF-8&dt=.%3ATSETMC%3A.%20%3A%3A%20%D8%B4%D8%B1%DA%A9%D8%AA%20%D9%85%D8%AF%DB%8C%D8%B1%DB%8C%D8%AA%20%D9%81%D9%86%D8%A7%D9%88%D8%B1%DB%8C%20%D8%A8%D9%88%D8%B1%D8%B3%20%D8%AA%D9%87%D8%B1%D8%A7%D9%86&sd=24-bit&sr=412x660&vp=980x1569&je=0&_u=IEBAAUAB~&jid=1703719345&gjid=393123024&cid=1673994265.1588976160&tid=UA-63076930-1&_gid=751187564.1588976160&_r=1&gtm=2ou4t0&z=901821990	2334.3980000354	2341.1500002258	603	35	200	image/gif	Image

Show Details

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)
1217.856	6.359
1228.091	1007.128
2242.165	8.554
2253.753	9.445
2268.545	17.019
2285.668	5.929
2297.471	11.309
2329.739	24.759
2380.275	5.576
2401.463	7.895
2415.051	194.834

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Tsetmc.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

Properly size images
Images can slow down the page's load time. Tsetmc.com should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Tsetmc.com should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Tsetmc.com should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Tsetmc.com should consider minifying JS files.

Remove unused CSS — Potential savings of 10 KB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Tsetmc.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

URL	Size (Bytes)	Potential Savings (Bytes)
input{font-family:Tahoma} ...	13274	10413

Show Details

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Tsetmc.com should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
(Start) http://tsetmc.com/	0
http://tsetmc.com/Loader.aspx?ParTree=15	630

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Tsetmc.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.

Diagnostics

Avoids enormous network payloads — Total size was 301 KB
Large network payloads can cost users money and are linked to long load times.

URL	Size (Bytes)
http://tsetmc.com/tsev2/res/loader.aspx?t=j&_469	135735
http://tsetmc.com/Loader.aspx?ParTree=15	84541
http://tsetmc.com/tsev2/res/loader.aspx?t=s&_469	35677
https://www.googletagmanager.com/gtag/js?id=UA-63076930-1	31177
https://www.google-analytics.com/analytics.js	19076
http://www.googleapis.com/	700
https://www.google-analytics.com/r/collect?v=1&_v=j82&a=450404267&t=pageview&_s=1&dl=http%3A%2F%2Ftsetmc.com%2FLoader.aspx%3FParTree%3D15&ul=en-us&de=UTF-8&dt=.%3ATSETMC%3A.%20%3A%3A%20%D8%B4%D8%B1%DA%A9%D8%AA%20%D9%85%D8%AF%DB%8C%D8%B1%DB%8C%D8%AA%20%D9%81%D9%86%D8%A7%D9%88%D8%B1%DB%8C%20%D8%A8%D9%88%D8%B1%D8%B3%20%D8%AA%D9%87%D8%B1%D8%A7%D9%86&sd=24-bit&sr=412x660&vp=980x1569&je=0&_u=IEBAAUAB~&jid=1703719345&gjid=393123024&cid=1673994265.1588976160&tid=UA-63076930-1&_gid=751187564.1588976160&_r=1&gtm=2ou4t0&z=901821990	603
http://tsetmc.com/	416

Show Details

Uses efficient cache policy on static assets — 1 resource found
Tsetmc.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)	Size (Bytes)
https://www.google-analytics.com/analytics.js	7200000	19076

Show Details

Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Tsetmc.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.

All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

Keep request counts low and transfer sizes small — 16 requests • 301 KB
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	16	307925
Other	4	172528
Document	1	84541
Script	2	50253
Image	9	603
Stylesheet	0	0
Media	0	0
Font	0	0
Third-party	12	51556

Show Details

Minimize third-party usage — Third-party code blocked the main thread for 40 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	Size (Bytes)	Main-Thread Blocking Time (Ms)
SHOW DETAILS	19679	39.232
SHOW DETAILS	31177	0

Show Details

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.

Metrics

First Contentful Paint — 5.8 s
The time taken for the first image or text on the page to be rendered.

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

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

Opportunities

Reduce server response times (TTFB) — Root document took 960 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.

Diagnostics

Avoid an excessive DOM size — 16,273 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		16,273
Maximum DOM Depth	SHOW DETAILS	17
Maximum Child Elements	SHOW DETAILS	1,112

Show Details

Reduce JavaScript execution time — 4.8 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
http://tsetmc.com/Loader.aspx?ParTree=15	4030.352	3881.524	132.448
Other	1410.904	610.276	3.648
https://www.google-analytics.com/analytics.js	97.176	92.66	4.516
https://www.googletagmanager.com/gtag/js?id=UA-63076930-1	75.24	64.572	10.668

Show Details

Minimize main-thread work — 5.6 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	4649.032
Other	347.136
Parse HTML & CSS	309.712
Script Parsing & Compilation	151.28
Style & Layout	112.5
Rendering	28.024
Garbage Collection	15.988

Show Details

Other

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

Accessibility

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

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`[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-*]` 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.

Audio and video

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

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

`<video>` elements contain a `<track>` element with `[kind="description"]`
Tsetmc.com may provide relevant information that dialogue cannot, by using audio descriptions.

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.

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` 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.

Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.

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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.

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.

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.

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

Show Details

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
فرابورس ایران
شبکه کدال
(2647.54)
(2242.78)
(2647.54)
(0.27)
(752.00)
(0.29)
(2242.78)
(0.72)
(1540.81)
(0.75)
(1051.25)
(0.08)
2999.10
0.42
(25826.51)
(1.27)
(3229.43)
1355.82
1252.3
(945.6)
855.35
757.39
(749.77)
3.09
(0.62)
0.66
3.72
3.54
1.74
(5)
(5)
(15.92)
4.42
1.48
8.21
9.99
3.77
1.5
(2.09)
(1.67)
(4.65)
(5)
(22.85)
21.48
(14.75)
13.47
12.57
(10.03)
(9.95)

Show Details

Internationalization and localization

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

Failing Elements
html

Show Details

Names and labels

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.

Failing Elements
a
a
a
a
a
a
a