9.8 sec in total
2 sec
7.5 sec
313 ms
Visit sdata.ir now to see the best up-to-date SData content for Iran and also check out these interesting facts you probably never knew about sdata.ir
سامانه آماری دادههای بازار، تحقیقات بازار و مطالعات بازار
Visit sdata.irWe analyzed Sdata.ir page load time and found that the first response time was 2 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
sdata.ir performance score
name
value
score
weighting
Value1.9 s
88/100
10%
Value2.5 s
90/100
25%
Value6.3 s
42/100
10%
Value1,110 ms
23/100
30%
Value0.173
69/100
15%
Value8.4 s
39/100
10%
1962 ms
380 ms
395 ms
397 ms
392 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 71% of them (94 requests) were addressed to the original Sdata.ir, 9% (12 requests) were made to Maps.googleapis.com and 5% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Sdata.ir.
Page size can be reduced by 1.7 MB (45%)
3.9 MB
2.1 MB
In fact, the total size of Sdata.ir main page is 3.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 108.4 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 108.4 kB or 86% of the original size.
Potential reduce by 99.7 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. SData images are well optimized though.
Potential reduce by 1.1 MB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.1 MB or 71% of the original size.
Potential reduce by 441.6 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Sdata.ir needs all CSS files to be minified and compressed as it can save up to 441.6 kB or 85% of the original size.
Number of requests can be reduced by 72 (62%)
116
44
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SData. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
1962 ms
wp-emoji-release.min.js
380 ms
style.css
395 ms
style.css
397 ms
styles.css
392 ms
styles-rtl.css
404 ms
style.css
573 ms
css
32 ms
userpro-rtl.min.css
807 ms
lightview.css
615 ms
userpro-jquery-ui.css
617 ms
style.css
621 ms
frontend-forms.css
715 ms
jquery-ui-1.9.1.custom.css
761 ms
style.css
1205 ms
woocommerce.css
841 ms
skin.css
845 ms
css
44 ms
css
54 ms
css
55 ms
css
56 ms
jquery.js
1282 ms
jquery-migrate.min.js
953 ms
tie.js
996 ms
core.min.js
1033 ms
datepicker.min.js
1037 ms
swfobject.js
61 ms
spinners.min.js
1150 ms
lightview.js
1384 ms
scripts.min.js
1421 ms
js
27 ms
frontend-form.js
1239 ms
plupload.full.min.js
1695 ms
handlers.min.js
1398 ms
jquery-ui-timepicker-addon.js
1640 ms
upload.js
1460 ms
userpro-emd.js
1585 ms
rtl.css
1589 ms
jquery.form.min.js
1460 ms
scripts.js
1629 ms
add-to-cart.min.js
1630 ms
jquery.blockUI.min.js
1691 ms
woocommerce.min.js
1718 ms
jquery.cookie.min.js
1553 ms
cart-fragments.min.js
1540 ms
conditional-logic.js
1541 ms
subscriptions.js
1623 ms
widget.min.js
1611 ms
position.min.js
1563 ms
menu.min.js
1519 ms
autocomplete.min.js
1476 ms
suggest.min.js
1535 ms
mouse.min.js
1602 ms
slider.min.js
1508 ms
tie-scripts.js
1714 ms
ilightbox.packed.js
1501 ms
wp-embed.min.js
1466 ms
search.js
1497 ms
cool-backgrounds-13.jpg
2384 ms
ir.png
683 ms
us.png
1042 ms
arab.png
1043 ms
es.png
1044 ms
Untitled-12.jpg
1043 ms
ameng.png
1044 ms
498434_JSIwqDWZ-512x330.jpg
1045 ms
498434_SC8u22Rg-110x75.png
1044 ms
498434_I42T3cGh-110x75.jpg
1045 ms
498434_JJXzlNwX-110x75.jpg
1075 ms
bds_4923.jpg
1688 ms
4thslider-1.jpg
1319 ms
OLAP_Cube-110x75.png
1162 ms
NormalDistributionWithPercentages-110x75.png
1165 ms
0000224.jpg
1272 ms
embed
192 ms
0000222.jpg
1517 ms
00002252.jpg
1316 ms
bigtheme-BNazanin.woff
1410 ms
s-BiyweUPV0v-yRb-cjciL3hpw3pgy2gAi-Ip7WPMi0.woff
62 ms
EFpQQyG9GqCrobXxL-KRMXbFhgvWbfSbdVg11QabG8w.woff
62 ms
fontawesome-webfont.woff
1585 ms
fontawesome-webfont.woff
1559 ms
bigtheme-BTitrBold.woff
1599 ms
BebasNeue-webfont.woff
1849 ms
bigtheme-BMitra.woff
1698 ms
js
77 ms
init_embed.js
33 ms
0000224-310x165.jpg
2007 ms
0000222-310x165.jpg
2016 ms
00002252-310x165.jpg
1821 ms
NormalDistributionWithPercentages-310x165.png
2114 ms
498434_JSIwqDWZ-310x165.jpg
2016 ms
common.js
40 ms
map.js
39 ms
google4.png
66 ms
overlay.js
63 ms
util.js
82 ms
onion.js
61 ms
search_impl.js
74 ms
StaticMapService.GetMapImage
218 ms
498434_SC8u22Rg-310x165.png
2170 ms
stats.js
86 ms
ViewportInfoService.GetViewportInfo
53 ms
transparent.png
45 ms
kh
93 ms
498434_I42T3cGh-310x165.jpg
1981 ms
498434_JJXzlNwX-310x165.jpg
1999 ms
controls.js
44 ms
vt
150 ms
vt
152 ms
vt
141 ms
vt
146 ms
vt
141 ms
sabtnam.jpg
2002 ms
vorod.jpg
2024 ms
css
62 ms
mapcnt6.png
32 ms
sv5.png
37 ms
sabtmaghale.jpg
2133 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
13 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
15 ms
Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff
17 ms
d-6IYplOFocCacKzxwXSOLO3LdcAZYWl9Si6vvxL-qU.woff
19 ms
sabtasr.jpg
2057 ms
AuthenticationService.Authenticate
320 ms
default_avatar_male.jpg
1708 ms
498434_JSIwqDWZ-110x75.jpg
1722 ms
EViews_multwin-110x75.png
1733 ms
64-9-110x47.jpg
1750 ms
stripe.png
1888 ms
sprite.png
1900 ms
blank.gif
1903 ms
sdata.ir accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
sdata.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
sdata.ir SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
FA
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sdata.ir can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it matches the claimed language. Our system also found out that Sdata.ir main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
sdata.ir
Open Graph data is detected on the main page of SData. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: