5.3 sec in total
540 ms
4.4 sec
401 ms
Welcome to ntn-pars.com homepage info - get ready to check NTNP Ars best content right away, or after learning these important things about ntn-pars.com
نوین طرح نیرو پارس تولید کننده ی تابلو های برق فشار متوسط و فشار ضعیف
Visit ntn-pars.comWe analyzed Ntn-pars.com page load time and found that the first response time was 540 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ntn-pars.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value7.7 s
3/100
25%
Value13.0 s
2/100
10%
Value170 ms
93/100
30%
Value0.014
100/100
15%
Value12.6 s
14/100
10%
540 ms
782 ms
192 ms
871 ms
1049 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that all of those requests were addressed to Ntn-pars.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Ntn-pars.com.
Page size can be reduced by 672.6 kB (20%)
3.4 MB
2.7 MB
In fact, the total size of Ntn-pars.com main page is 3.4 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. 55% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 17.1 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. This page needs HTML code to be minified as it can gain 5.4 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.1 kB or 83% of the original size.
Potential reduce by 2.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. NTNP Ars images are well optimized though.
Potential reduce by 210.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 210.7 kB or 70% of the original size.
Potential reduce by 442.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. Ntn-pars.com needs all CSS files to be minified and compressed as it can save up to 442.1 kB or 86% of the original size.
Number of requests can be reduced by 20 (48%)
42
22
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NTNP Ars. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
ntn-pars.com
540 ms
ntn-pars.com
782 ms
font-face.css
192 ms
bootstrap.min.css
871 ms
icofont.min.css
1049 ms
font-awesome.min.css
882 ms
ionicons.min.css
940 ms
animate.min.css
1080 ms
venobox.css
911 ms
owl.carousel.min.css
1043 ms
aos.css
1055 ms
style.css
1266 ms
CustomCss.css
1108 ms
jquery.min.js
1213 ms
bootstrap.bundle.min.js
1372 ms
jquery.easing.min.js
1235 ms
jquery.waypoints.min.js
1283 ms
counterup.min.js
1283 ms
isotope.pkgd.min.js
1405 ms
venobox.min.js
1415 ms
owl.carousel.min.js
1472 ms
aos.js
1462 ms
bootstrap-rtl.min.css
1471 ms
main.js
1599 ms
logo.jpg
221 ms
language.png
222 ms
user.png
223 ms
19890d01e6ce4b9aba2fc75ebbae02a5.jpg
1048 ms
5b88d6766d414ddb97b1452f8a34aeee.jpg
1026 ms
about-bg.jpg
698 ms
d0968821ab8143bfb1d1a8bfc2a51590.jpg
352 ms
8f585b82d4b74f27a78c5525a3461a65.jpg
709 ms
8c46d88720a342e98f04a82714ae5594.jpg
539 ms
3a910afbfa574031a8f4f477253466e2.jpg
527 ms
49a0ac4dc06a42a1b62831ba90f0c0cc.jpg
703 ms
a48a89ed314f47549e693bc7666bb895.jpg
720 ms
d49ddfa1eb1c41ff80eefaf40c1fa7a6.jpg
868 ms
4f9aa38388414970b065cd635f096e95.jpg
877 ms
0b00415932b140dfa0b64478398e0c07.jpg
888 ms
e769a00149b548fcaf85b9d98189a075.png
899 ms
f518c76877c84a8a8263c0472b72602c.png
1042 ms
be25f3ffcf72498c9a7b708723a2eb9e.png
1049 ms
d524413c8c024bb6972e58891fb69c51.png
1068 ms
f900d180197a41e1b6d963e070cd317c.png
1081 ms
Vazir-Regular.woff
1107 ms
Vazir-Medium.woff
1122 ms
Vazir-Light.woff
1159 ms
Vazir-Thin.woff
1158 ms
Vazir-Bold.woff
1159 ms
Vazir-Black.woff
1178 ms
ionicons.ttf
1301 ms
icofont.woff
1448 ms
ntn-pars.com 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
ARIA input fields do not have accessible names
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
ntn-pars.com 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
ntn-pars.com 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
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ntn-pars.com can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ntn-pars.com 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.
ntn-pars.com
Open Graph description is not detected on the main page of NTNP Ars. 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: