8.2 sec in total
498 ms
6.9 sec
781 ms
Welcome to naffire.com homepage info - get ready to check NAF Fire best content right away, or after learning these important things about naffire.com
A family owned company, was established in 1992 in Amman-Jordan, Nasr Awwadeh Factory (NAF). Since 1992 we have grown to become one of the main distributors for more than 20 international brands.
Visit naffire.comWe analyzed Naffire.com page load time and found that the first response time was 498 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
naffire.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value6.2 s
11/100
25%
Value12.6 s
3/100
10%
Value720 ms
41/100
30%
Value0.44
21/100
15%
Value9.4 s
30/100
10%
498 ms
1059 ms
494 ms
1175 ms
1205 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 92% of them (105 requests) were addressed to the original Naffire.com, 6% (7 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Naffire.com.
Page size can be reduced by 512.7 kB (13%)
4.0 MB
3.5 MB
In fact, the total size of Naffire.com main page is 4.0 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 3.5 MB which makes up the majority of the site volume.
Potential reduce by 72.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 18.9 kB, which is 23% 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 72.1 kB or 88% of the original size.
Potential reduce by 378.5 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, NAF Fire needs image optimization as it can save up to 378.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 55.5 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 55.5 kB or 17% of the original size.
Potential reduce by 6.5 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. Naffire.com has all CSS files already compressed.
Number of requests can be reduced by 22 (22%)
100
78
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NAF Fire. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
naffire.com
498 ms
naffire.com
1059 ms
plugins.css
494 ms
style.css
1175 ms
custom.js
1205 ms
jquery.themepunch.tools.min.js
923 ms
jquery.themepunch.revolution.min.js
1005 ms
pe-icon-7-stroke.css
741 ms
font-awesome.css
713 ms
settings.css
949 ms
revolution.addon.polyfold.css
994 ms
revolution.addon.polyfold.min.js
1178 ms
revolution.extension.actions.min.js
1190 ms
revolution.extension.carousel.min.js
1287 ms
revolution.extension.kenburn.min.js
1256 ms
revolution.extension.layeranimation.min.js
1393 ms
revolution.extension.migration.min.js
1390 ms
revolution.extension.navigation.min.js
1440 ms
revolution.extension.parallax.min.js
1424 ms
revolution.extension.slideanims.min.js
1513 ms
revolution.extension.video.min.js
1504 ms
js
55 ms
jquery.js
1628 ms
plugins.js
1866 ms
functions.js
1663 ms
css
32 ms
logo-2.png
455 ms
logo.png
524 ms
1581928267499.jpg
531 ms
15819300207381.jpg
784 ms
15820936182874.jpg
785 ms
15825877674012.jpg
786 ms
15819289868307.jpg
788 ms
15825877423752.jpg
787 ms
15820943571604.jpg
878 ms
15819301616868.jpg
890 ms
15819299275356.jpg
909 ms
15819297769173.jpg
931 ms
158258807374.jpg
1070 ms
15816123224060.jpg
1251 ms
15816123225699.jpg
1342 ms
1583282435986.jpg
1348 ms
15832824364864.jpg
1142 ms
15832824366491.jpg
1171 ms
15832824948338.jpg
1491 ms
15832824953427.jpg
1385 ms
15832824956965.jpg
1647 ms
15832826371012.jpg
1727 ms
15832826372229.jpg
1583 ms
15832826373495.jpg
1578 ms
15728891088588.png
1621 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
78 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
79 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
98 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
108 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
109 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
108 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
109 ms
fa-brands-400.woff
1974 ms
fa-solid-900.woff
1789 ms
fa-regular-400.woff
1657 ms
inspiro-icons.ttf
1724 ms
15728891089281.png
1691 ms
15728891089886.png
1752 ms
1572889109636.png
1782 ms
15728891091321.png
1754 ms
15728891091950.png
1701 ms
15728891092770.png
1707 ms
15728891093433.png
1760 ms
15728891094003.png
1726 ms
15728891094425.png
1769 ms
revicons.woff
1526 ms
15728891094923.png
1581 ms
15728891095478.png
1612 ms
15728891096004.png
1677 ms
15728891096477.png
1704 ms
15728891097132.png
1754 ms
15728891097664.png
1661 ms
15728891098220.png
1720 ms
15728891098864.png
1727 ms
15728891099380.png
1810 ms
15728891101.png
1704 ms
1572889110824.png
1629 ms
15728891102080.png
1616 ms
15728891103069.png
1601 ms
15728891104082.png
1769 ms
15728891105108.png
1636 ms
15728891106148.png
1627 ms
15728891106752.png
1529 ms
15728891107568.png
1440 ms
15728891108212.png
1514 ms
15728891108781.png
1624 ms
15728891109663.png
1599 ms
1572889111625.png
1528 ms
15728891111581.png
1411 ms
15728891112092.png
1466 ms
15728891112823.png
1683 ms
15728891113497.png
1588 ms
15728891114164.png
1512 ms
15728891114978.png
1468 ms
15728891116205.png
1448 ms
15728891117457.png
1535 ms
15820967938717.png
1625 ms
15820969261124.png
1584 ms
15820969658647.png
1534 ms
15820973716084.png
1507 ms
15820977944845.png
1521 ms
15820977946510.png
1524 ms
15820960267081.png
1597 ms
15820980725615.png
1617 ms
15820983876411.png
1531 ms
15820977947157.png
1513 ms
logo-powerd.png
1516 ms
world-map.png
1560 ms
naffire.com 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
naffire.com 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
naffire.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Naffire.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Naffire.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.
naffire.com
Open Graph description is not detected on the main page of NAF Fire. 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: