4.5 sec in total
511 ms
3.6 sec
363 ms
Click here to check amazing Fireline Co content. Otherwise, check out these important facts you probably never knew about fireline.co.ke
Fireline Safety Kenya is a registered and certified company that specializes in the supply, installation and maintenance of fire protection and security products
Visit fireline.co.keWe analyzed Fireline.co.ke page load time and found that the first response time was 511 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
fireline.co.ke performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value6.4 s
9/100
25%
Value10.1 s
9/100
10%
Value920 ms
30/100
30%
Value0.001
100/100
15%
Value12.5 s
14/100
10%
511 ms
16 ms
199 ms
193 ms
198 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 73% of them (71 requests) were addressed to the original Fireline.co.ke, 11% (11 requests) were made to Platform.twitter.com and 9% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fireline.co.ke.
Page size can be reduced by 77.4 kB (5%)
1.6 MB
1.5 MB
In fact, the total size of Fireline.co.ke main page is 1.6 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 28.5 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 9.2 kB, which is 26% 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 28.5 kB or 80% of the original size.
Potential reduce by 34.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. Fireline Co images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 11.4 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. Fireline.co.ke needs all CSS files to be minified and compressed as it can save up to 11.4 kB or 14% of the original size.
Number of requests can be reduced by 43 (54%)
80
37
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fireline Co. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
fireline.co.ke
511 ms
css
16 ms
bootstrap.css
199 ms
settings.css
193 ms
font-awesome.min.css
198 ms
plugins.css
292 ms
style.css
205 ms
social.css
209 ms
switcher.css
289 ms
font-awesome.min.css
31 ms
widgets.js
110 ms
jquery-1.11.2.min.js
339 ms
jquery-migrate-1.2.1.min.js
287 ms
bootstrap.min.js
338 ms
jquery.themepunch.tools.min.js
392 ms
jquery.themepunch.revolution.min.js
476 ms
plugins.js
576 ms
custom.js
404 ms
styleswitch.js
405 ms
logo.png
404 ms
fire-extinguishing.jpg
674 ms
powder-fire-extinguisher.jpg
482 ms
Fire-Blankets.jpg
483 ms
Smoke-alarm.jpg
485 ms
Foam-fire-extinguishers.jpg
572 ms
co2-extinguisher.jpg
627 ms
water-extinguisher.jpg
628 ms
AFFF-foam-extinguishers.jpg
628 ms
firealarm.jpg
671 ms
foam-extinguisher.jpg
673 ms
PSV-first-aid-kit.jpg
678 ms
rambojet.jpg
679 ms
hosepipe.jpg
773 ms
client1.png
762 ms
client3.png
770 ms
client8.png
771 ms
client9.png
771 ms
client10.png
772 ms
client11.png
857 ms
client12.png
861 ms
client13.png
673 ms
client14.png
667 ms
client15.png
668 ms
css
13 ms
client16.png
664 ms
client17.png
751 ms
client2.png
674 ms
client4.png
660 ms
client18.png
627 ms
client19.png
611 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff
7 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff
12 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff
24 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrc.woff
190 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrc.woff
184 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff
22 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff
23 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrc.woff
93 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrc.woff
348 ms
fontawesome-webfont.woff
21 ms
imge1.jpg
609 ms
imge2.jpg
648 ms
imge3.jpg
652 ms
footersmiley-icon.png
653 ms
fire_2.jpg
1133 ms
1.jpg
676 ms
shadow.png
576 ms
style.css
663 ms
back-to-top.png
665 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
67 ms
settings
98 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
26 ms
FirelineSafetyk
115 ms
polyfills-3b821eda8863adcc4a4b.js
26 ms
runtime-a697c5a1ae32bd7e4d42.js
50 ms
modules.20f98d7498a59035a762.js
78 ms
main-fd9ef5eb169057cda26d.js
86 ms
_app-88bf420a57d49e33be53.js
92 ms
%5BscreenName%5D-c33f0b02841cffc3e9b4.js
94 ms
_buildManifest.js
97 ms
_ssgManifest.js
99 ms
color1.css
98 ms
color2.css
97 ms
color3.css
97 ms
color4.css
98 ms
color5.css
97 ms
color6.css
97 ms
color7.css
97 ms
color8.css
97 ms
color9.css
97 ms
color10.css
96 ms
color11.css
98 ms
color12.css
97 ms
color13.css
97 ms
color14.css
97 ms
box1.css
97 ms
footer1.css
96 ms
fireline.co.ke 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
fireline.co.ke 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fireline.co.ke 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fireline.co.ke 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 Fireline.co.ke 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.
fireline.co.ke
Open Graph description is not detected on the main page of Fireline Co. 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: