Tools & Wizards About Us
fenixfires.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

fenixfires.com

Fenix Fire Solution | fenixfires.com - Fire Safety , Fire Solutions & fire extinguisher

Page Load Speed

4.4 sec in total

First Response

330 ms

Resources Loaded

3.7 sec

Page Rendered

332 ms

fenixfires.com screenshot

About Website

Click here to check amazing Fenix Fire S content. Otherwise, check out these important facts you probably never knew about fenixfires.com

Fenix Fire Solution | fenixfires.com, Indore based India's most trusted Fire Safety brand for fire, security and project solutions

Visit fenixfires.com

Key Findings

We analyzed Fenixfires.com page load time and found that the first response time was 330 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

fenixfires.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

fenixfires.com

330 ms

bootstrap.css

377 ms

theme.css

399 ms

revslider.css

270 ms

custom.css

277 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 96% of them (50 requests) were addressed to the original Fenixfires.com, 2% (1 request) were made to Google.com and 2% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Fenixfires.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 361.6 kB (12%)

Content Size

3.1 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fenixfires.com main page is 3.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. 45% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 62.4 kB

  • Original 69.1 kB
  • After minification 45.6 kB
  • After compression 6.8 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 23.5 kB, which is 34% 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 62.4 kB or 90% of the original size.

Image Optimization

-10%

Potential reduce by 285.9 kB

  • Original 2.8 MB
  • After minification 2.6 MB

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. Fenix Fire S images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 5.1 kB

  • Original 164.8 kB
  • After minification 164.8 kB
  • After compression 159.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.

CSS Optimization

-13%

Potential reduce by 8.2 kB

  • Original 62.0 kB
  • After minification 62.0 kB
  • After compression 53.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. Fenixfires.com needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (27%)

Requests Now

48

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fenix Fire S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fenixfires.com

fenixfires.com

330 ms

bootstrap.css

bootstrap.css

377 ms

theme.css

theme.css

399 ms

revslider.css

revslider.css

270 ms

custom.css

custom.css

277 ms

jssor.slider.min.js

jssor.slider.min.js

390 ms

email-decode.min.js

email-decode.min.js

11 ms

jquery.min.js

jquery.min.js

451 ms

jquery-ui.min.js

jquery-ui.min.js

288 ms

bootstrap.min.js

bootstrap.min.js

524 ms

modules.js

modules.js

660 ms

theme.js

theme.js

628 ms

fs_gallery.js

fs_gallery.js

648 ms

jquery.isotope.min.js

jquery.isotope.min.js

650 ms

sorting.js

sorting.js

652 ms

logo.png

logo.png

473 ms

logo.png

logo.png

461 ms

loading.gif

loading.gif

486 ms

1.jpg

1.jpg

827 ms

2.jpg

2.jpg

833 ms

3.jpg

3.jpg

968 ms

4.jpg

4.jpg

949 ms

5.jpg

5.jpg

1077 ms

6.jpg

6.jpg

1329 ms

7.jpg

7.jpg

1323 ms

8.jpg

8.jpg

1550 ms

9.jpg

9.jpg

1547 ms

10.jpg

10.jpg

1461 ms

11.jpg

11.jpg

1797 ms

12.jpg

12.jpg

1806 ms

13.jpg

13.jpg

1816 ms

14.jpg

14.jpg

1957 ms

b05.png

b05.png

1797 ms

a22.png

a22.png

1811 ms

home-icon1.png

home-icon1.png

2046 ms

home-icon2.png

home-icon2.png

2048 ms

home-icon3.png

home-icon3.png

2070 ms

home.jpg

home.jpg

2414 ms

sprite.png

sprite.png

2067 ms

hydrant.jpg

hydrant.jpg

2328 ms

water.jpg

water.jpg

2408 ms

foam.jpg

foam.jpg

2412 ms

powder.jpg

powder.jpg

2432 ms

co2.jpg

co2.jpg

2412 ms

fa.woff

fa.woff

2797 ms

embed

embed

305 ms

item1.jpg

item1.jpg

2671 ms

acc1.png

acc1.png

2703 ms

acc2.png

acc2.png

2671 ms

acc3.png

acc3.png

2688 ms

logo-foot.png

logo-foot.png

2577 ms

js

js

61 ms

Accessibility Review

fenixfires.com accessibility score

67

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

fenixfires.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fenixfires.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fenixfires.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Fenixfires.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.

Social Sharing Optimization

fenixfires.com

Open Graph description is not detected on the main page of Fenix Fire S. 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: