3.7 sec in total
683 ms
2.5 sec
562 ms
Visit 14ma.ir now to see the best up-to-date 14 Ma content and also check out these interesting facts you probably never knew about 14ma.ir
Visit 14ma.irWe analyzed 14ma.ir page load time and found that the first response time was 683 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
14ma.ir performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value22.6 s
0/100
25%
Value37.4 s
0/100
10%
Value1,300 ms
18/100
30%
Value0.001
100/100
15%
Value20.9 s
2/100
10%
683 ms
112 ms
197 ms
195 ms
198 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that all of those requests were addressed to 14ma.ir and no external sources were called. The less responsive or slowest element that took the longest time to load (922 ms) belongs to the original domain 14ma.ir.
Page size can be reduced by 588.4 kB (40%)
1.5 MB
882.0 kB
In fact, the total size of 14ma.ir main page is 1.5 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. 30% of websites need less resources to load. Images take 863.0 kB which makes up the majority of the site volume.
Potential reduce by 25.2 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 25.2 kB or 78% of the original size.
Potential reduce by 143.9 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. Obviously, 14 Ma needs image optimization as it can save up to 143.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 340.2 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 340.2 kB or 71% of the original size.
Potential reduce by 79.1 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. 14ma.ir needs all CSS files to be minified and compressed as it can save up to 79.1 kB or 84% of the original size.
Number of requests can be reduced by 32 (52%)
62
30
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 14 Ma. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
14ma.ir
683 ms
style.css
112 ms
typo.css
197 ms
slimbox.css
195 ms
style.css
198 ms
style.css
199 ms
style.css
206 ms
mod_jaslideshow.css
225 ms
mootools-core.js
387 ms
core.js
300 ms
mootools-more.js
572 ms
script.js
310 ms
caption.js
313 ms
slimbox.js
331 ms
script.js
407 ms
system.css
416 ms
general.css
421 ms
template.css
437 ms
jquery.js
607 ms
script.js
510 ms
mod_g_prayer_times.php
522 ms
system.css
109 ms
Bottom_texture.jpg
655 ms
sheet_b.png
123 ms
sheet_t.png
117 ms
sheet.png
123 ms
nav.png
119 ms
menuseparator.png
121 ms
menuitem.png
215 ms
spacer.gif
213 ms
subitem.png
212 ms
block_b.png
215 ms
block_t.png
222 ms
block.png
316 ms
blockcontent_b.png
317 ms
blockcontent_t.png
317 ms
blockcontent.png
320 ms
425h3_938_260.jpg
518 ms
1_938_260.jpg
508 ms
preloader.gif
422 ms
vmenublockheader.png
404 ms
vmenuitem.png
408 ms
S1.gif
509 ms
S2.gif
509 ms
S3.gif
515 ms
S4.gif
596 ms
11---0001366.jpg
617 ms
hamkari.png
629 ms
blockheader.png
615 ms
s-flash.gif
616 ms
mod_jaslideshow_rtl.css
678 ms
flasher.gif
630 ms
tgt55%201_130_90.JPG
638 ms
fitileh%207_130_90.JPG
640 ms
kar%201_130_90.JPG
641 ms
aaa22.JPG
654 ms
hamayesh2.jpg
720 ms
fetr111.jpg
822 ms
hesab303.jpg
838 ms
371223_440.jpg
922 ms
002255895.jpg
759 ms
footer_b.png
756 ms
footer.png
820 ms
button.png
255 ms
14ma.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
14ma.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
14ma.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 14ma.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 14ma.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.
14ma.ir
Open Graph description is not detected on the main page of 14 Ma. 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: