3.3 sec in total
492 ms
2.5 sec
290 ms
Welcome to npack.ir homepage info - get ready to check Npack best content for Iran right away, or after learning these important things about npack.ir
نام آوران تولید و عرضه کننده مستقیم هدایای تبلیغاتی خاص و ارزان | هدیه تبلیغاتی نام آوران | شماره های تماس 01342134318 - 01342134319
Visit npack.irWe analyzed Npack.ir page load time and found that the first response time was 492 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
npack.ir performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value3.3 s
68/100
25%
Value13.1 s
2/100
10%
Value380 ms
70/100
30%
Value0.138
79/100
15%
Value8.8 s
35/100
10%
492 ms
88 ms
201 ms
205 ms
220 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 73% of them (82 requests) were addressed to the original Npack.ir, 12% (13 requests) were made to Maps.google.com and 6% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (724 ms) belongs to the original domain Npack.ir.
Page size can be reduced by 975.2 kB (56%)
1.7 MB
767.2 kB
In fact, the total size of Npack.ir main page is 1.7 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. 65% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 51.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 51.4 kB or 79% of the original size.
Potential reduce by 25.2 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. Npack images are well optimized though.
Potential reduce by 699.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 699.7 kB or 69% of the original size.
Potential reduce by 198.8 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. Npack.ir needs all CSS files to be minified and compressed as it can save up to 198.8 kB or 84% of the original size.
Number of requests can be reduced by 71 (72%)
99
28
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Npack. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
npack.ir
492 ms
wp-emoji-release.min.js
88 ms
styles.css
201 ms
styles-rtl.css
205 ms
tp_twitter_plugin.css
220 ms
settings.css
224 ms
captions.php
228 ms
style.css
226 ms
prettyPhoto.css
281 ms
owl.carousel.css
284 ms
owl.theme.css
304 ms
jquery.ui.all.css
307 ms
responsive.css
308 ms
images.css
311 ms
style.css
361 ms
style.php
419 ms
exo.css
387 ms
jquery.js
484 ms
jquery-migrate.min.js
394 ms
jquery.themepunch.plugins.min.js
483 ms
jquery.themepunch.revolution.min.js
525 ms
rtl.css
471 ms
custom.css
478 ms
css
25 ms
jquery.form.min.js
498 ms
scripts.js
556 ms
core.min.js
561 ms
widget.min.js
566 ms
mouse.min.js
566 ms
sortable.min.js
579 ms
tabs.min.js
603 ms
accordion.min.js
640 ms
owl.carousel.min.js
647 ms
jquery.swiper.min.js
651 ms
jquery.plugins.js
654 ms
mfn.menu.js
658 ms
mfn.fsa.js
683 ms
js
24 ms
scripts.js
724 ms
comment-reply.min.js
653 ms
wp-embed.min.js
545 ms
fonts.css
523 ms
base.css
524 ms
buttons.css
548 ms
grid.css
593 ms
layout.css
598 ms
variables.css
547 ms
shortcodes.css
551 ms
animations.css
525 ms
jquery.ui.base.css
546 ms
jquery.ui.theme.css
595 ms
fontawesome.css
164 ms
socialico.css
161 ms
socialico-plus.css
167 ms
jquery.ui.core.css
87 ms
jquery.ui.accordion.css
84 ms
jquery.ui.tabs.css
136 ms
home_corporate_1.jpg
408 ms
LogoNPA.png
109 ms
dummy.png
109 ms
testimonials_8.png
108 ms
testimonials_7.png
111 ms
testimonials_6.png
301 ms
testimonials_5.png
109 ms
testimonials_4.png
303 ms
testimonials_3.png
305 ms
testimonials_2.png
304 ms
testimonials_1.png
304 ms
list_tick.png
292 ms
exo-regular-webfont.woff
390 ms
exo-light-webfont.woff
389 ms
exo-thin-webfont.woff
292 ms
exo-bold-webfont.woff
389 ms
BYekan.woff
389 ms
socialico-webfont.woff
291 ms
fontawesome-webfont.woff
458 ms
blockquote.png
345 ms
portfolio_section.png
343 ms
common.js
30 ms
map.js
30 ms
util.js
30 ms
marker.js
30 ms
timer.png
169 ms
slider_controls.png
170 ms
rev_slide_2.jpg
463 ms
ajax-loader.gif
171 ms
blockquote_bg.png
171 ms
faq_controls.png
226 ms
Kufi.woff
272 ms
StaticMapService.GetMapImage
81 ms
onion.js
32 ms
openhand_8_8.cur
23 ms
ViewportInfoService.GetViewportInfo
54 ms
stats.js
50 ms
controls.js
19 ms
transparent.png
42 ms
css
16 ms
vt
44 ms
google4.png
41 ms
vt
41 ms
vt
59 ms
vt
57 ms
vt
58 ms
pin_small.png
86 ms
mapcnt6.png
21 ms
sv5.png
11 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
8 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
17 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
17 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
17 ms
tmapctrl.png
14 ms
tmapctrl4.png
14 ms
AuthenticationService.Authenticate
246 ms
npack.ir accessibility score
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
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.
npack.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
npack.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
FA
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Npack.ir can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it does not match the claimed English language. Our system also found out that Npack.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.
npack.ir
Open Graph description is not detected on the main page of Npack. 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: