7.3 sec in total
658 ms
6.1 sec
566 ms
Visit a-fire.com now to see the best up-to-date A FIRE content and also check out these interesting facts you probably never knew about a-fire.com
Create Your bio fireplace & build hearth fireplaces with A-FIRE. A range of remote controlled modern and design fireplaces easy to install and to use
Visit a-fire.comWe analyzed A-fire.com page load time and found that the first response time was 658 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
a-fire.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value18.7 s
0/100
25%
Value10.3 s
8/100
10%
Value1,280 ms
18/100
30%
Value0.049
99/100
15%
Value17.6 s
4/100
10%
658 ms
1380 ms
641 ms
877 ms
883 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 70% of them (67 requests) were addressed to the original A-fire.com, 6% (6 requests) were made to Apis.google.com and 5% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain A-fire.com.
Page size can be reduced by 227.5 kB (21%)
1.1 MB
857.4 kB
In fact, the total size of A-fire.com main page is 1.1 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. Javascripts take 484.1 kB which makes up the majority of the site volume.
Potential reduce by 75.6 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 11.4 kB, which is 13% 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 75.6 kB or 85% of the original size.
Potential reduce by 93 B
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. A FIRE images are well optimized though.
Potential reduce by 118.1 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 118.1 kB or 24% of the original size.
Potential reduce by 33.7 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. A-fire.com needs all CSS files to be minified and compressed as it can save up to 33.7 kB or 31% of the original size.
Number of requests can be reduced by 38 (44%)
86
48
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A 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 24 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
a-fire.com
658 ms
a-fire.com
1380 ms
module.css
641 ms
default.css
877 ms
skin.css
883 ms
portal.css
879 ms
jquery.min.js
1326 ms
dnncore.js
912 ms
ScriptResource.axd
1344 ms
dnn.js
1100 ms
dnn.xml.js
1102 ms
dnn.xml.jsparser.js
1102 ms
dnn.xmlhttp.js
1144 ms
dnn.xmlhttp.jsxmlhttprequest.js
1316 ms
widgets.js
47 ms
skypeCheck.js
17 ms
plusone.js
35 ms
initWidgets.js
922 ms
call_green_white_153x63.png
10 ms
lg-share-en.gif
237 ms
logoImage.gif
330 ms
EnglishFlag.gif
356 ms
frenchFlag.gif
346 ms
germanFlag.gif
352 ms
ItalianFlag.gif
334 ms
Flagbig2.gif
340 ms
nederland.bmp
558 ms
brazil.png
566 ms
spacer.gif
574 ms
twitter.png
573 ms
facebookImag.gif
567 ms
blogger.jpg
574 ms
youtube_fire.png
806 ms
ventless-fireplace-bio.JPG
1019 ms
ethanol-burner-a-fire.jpg
1436 ms
Electronic_ethanol_fireplaces_remote_controlled.jpg
1015 ms
information.gif
810 ms
ventless_fireplaces%20(2).JPG
805 ms
ethanol-burner-bio.jpg
1043 ms
ethanol-fireplaces.jpg
1036 ms
design-bio_ethanol_burner.JPG
1489 ms
ethanol_stove_afire.jpg
1246 ms
direct_vent_fireplace_concorde1.jpg
1241 ms
ventless-fireplace-with-ethanol-burner.jpg
1483 ms
Remote-controll.JPG
1275 ms
00emial.jpg
1463 ms
bio_ethanol_burner.jpg
1904 ms
Bio-ethanol-burner-embedded-BL66.JPG
1729 ms
ethanol_burners_assembly_afire.jpg
1712 ms
ethanol_fireplaces_wharehouse_afire.jpg
1716 ms
ventless_ethanol_burner_a-fire.jpg
1732 ms
ethanol-fireplace-BE150.JPG
1949 ms
Bio-burner-BL108-Top.jpg
1947 ms
SolPartMenu.min.js
1961 ms
ethnaol_burner_xl_afire.jpg
1946 ms
Burner.jpg
1957 ms
ethanol_fireplaces.JPG
1808 ms
BL108-ethanol-burner-afire.jpg
1875 ms
bio-burner-3XL.JPG
1873 ms
modulo-L-ethanol-burner-insert-225-75.JPG
2391 ms
ventless_ethanol_burner_afire.jpg
1861 ms
ethanol_fireplace_afire.jpg
1900 ms
bg.jpg
719 ms
ver_Rep.gif
720 ms
facebook_CoImage.gif
746 ms
menuRep.gif
737 ms
lg-share-en.gif
21 ms
nMzWPdY1Lf4
187 ms
hit.xiti
20 ms
cb=gapi.loaded_0
12 ms
cb=gapi.loaded_1
82 ms
fastbutton
78 ms
DotNetNukeAjaxShared.js
668 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
211 ms
spacer.gif
601 ms
breadcrumb.gif
601 ms
menuSep.gif
824 ms
HoriRep.jpg
825 ms
postmessageRelay
86 ms
www-player.css
17 ms
www-embed-player.js
52 ms
base.js
134 ms
developers.google.com
521 ms
3604799710-postmessagerelay.js
447 ms
rpc:shindig_random.js
65 ms
settings
427 ms
ad_status.js
274 ms
4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js
192 ms
embed.js
56 ms
cb=gapi.loaded_0
57 ms
widgets.js
364 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
206 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
210 ms
button.856debeac157d9669cf51e73a08fbc93.js
171 ms
id
132 ms
Create
127 ms
a-fire.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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
a-fire.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
a-fire.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A-fire.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 A-fire.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.
a-fire.com
Open Graph description is not detected on the main page of A 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: