7.6 sec in total
647 ms
6.3 sec
658 ms
Welcome to tejar.ir homepage info - get ready to check Tejar best content for Iran right away, or after learning these important things about tejar.ir
Visit tejar.irWe analyzed Tejar.ir page load time and found that the first response time was 647 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
tejar.ir performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value9.0 s
1/100
25%
Value12.4 s
3/100
10%
Value470 ms
60/100
30%
Value0.572
12/100
15%
Value10.0 s
26/100
10%
647 ms
3581 ms
568 ms
580 ms
587 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 89% of them (54 requests) were addressed to the original Tejar.ir, 10% (6 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Tejar.ir.
Page size can be reduced by 198.1 kB (23%)
859.8 kB
661.6 kB
In fact, the total size of Tejar.ir main page is 859.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 384.3 kB which makes up the majority of the site volume.
Potential reduce by 134.8 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 134.8 kB or 82% of the original size.
Potential reduce by 9.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. Tejar images are well optimized though.
Potential reduce by 31.7 kB
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 31.7 kB or 15% of the original size.
Potential reduce by 21.9 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. Tejar.ir needs all CSS files to be minified and compressed as it can save up to 21.9 kB or 21% of the original size.
Number of requests can be reduced by 43 (81%)
53
10
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tejar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
tejar.ir
647 ms
tejar.ir
3581 ms
theme.min.css
568 ms
style.css
580 ms
style.min.css
587 ms
header-footer.min.css
587 ms
frontend-lite-rtl.min.css
835 ms
post-6.css
757 ms
all.min.css
774 ms
v4-shims.min.css
781 ms
public.css
785 ms
front-rtl.css
906 ms
style.css
945 ms
swiper.min.css
973 ms
frontend-lite-rtl.min.css
976 ms
font.css
979 ms
global.css
1035 ms
post-10.css
1100 ms
post-30.css
1134 ms
post-1428.css
1165 ms
css
30 ms
jquery.min.js
1449 ms
jquery-migrate.min.js
1186 ms
widget-nav-menu-rtl.min.css
1244 ms
widget-carousel-rtl.min.css
736 ms
widget-posts-rtl.min.css
750 ms
widget-icon-box-rtl.min.css
652 ms
animations.min.css
679 ms
post-2381.css
727 ms
hello-frontend.min.js
832 ms
hooks.min.js
832 ms
vue.min.js
1061 ms
jet-menu-public-scripts.js
962 ms
flatpickr.min.js
989 ms
flatpickr-mobile.js
961 ms
jquery.smartmenus.min.js
995 ms
imagesloaded.min.js
993 ms
webpack-pro.runtime.min.js
1153 ms
webpack.runtime.min.js
1148 ms
frontend-modules.min.js
1232 ms
i18n.min.js
1202 ms
frontend.min.js
1197 ms
waypoints.min.js
1254 ms
core.min.js
1316 ms
frontend.min.js
1327 ms
elements-handlers.min.js
1350 ms
widgets-scripts.js
1331 ms
logo3-1.png
681 ms
001_Majma-300x300.jpg
701 ms
002_Laghv-300x300.jpg
806 ms
003_Majma-Final--300x300.jpg
873 ms
logo002.png
1048 ms
SL002.jpg
1016 ms
el0ncxwwdydz.png
1263 ms
1083687_orig-1.png
1073 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
79 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
79 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
119 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
129 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
130 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
130 ms
tejar.ir accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
tejar.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
tejar.ir SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
FA
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tejar.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 Tejar.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.
tejar.ir
Open Graph description is not detected on the main page of Tejar. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: