Access aizenfire.com. Los Angeles Fire Protection & Extinguisher Companies | Fire Extinguishing & Suppression Systems

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value22.0 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value2,150 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.278

44/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

aizenfire.com

245 ms

aizenfire.com

2525 ms

wp-emoji-release.min.js

111 ms

custom.css

183 ms

nivo-lightbox.css

186 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 78% of them (97 requests) were addressed to the original Aizenfire.com, 5% (6 requests) were made to Youtube.com and 4% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Webbased.com.

Content Size

2.2 MB

After Optimization

2.0 MB

In fact, the total size of Aizenfire.com main page is 2.2 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. Only a small number of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 102.2 kB

Original 123.3 kB
After minification 119.8 kB
After compression 21.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. 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 102.2 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 395 B

Original 1.4 MB
After minification 1.4 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. Aizen Fire images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 93.3 kB

Original 514.3 kB
After minification 506.6 kB
After compression 421.0 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 93.3 kB or 18% of the original size.

CSS Optimization

-21%

Potential reduce by 43.3 kB

Original 203.2 kB
After minification 203.2 kB
After compression 159.9 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. Aizenfire.com needs all CSS files to be minified and compressed as it can save up to 43.3 kB or 21% of the original size.

Requests Now

101

After Optimization

The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aizen 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 35 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Some elements have a [tabindex] value greater than 0

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA IDs are not unique

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aizenfire.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 Aizenfire.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

aizenfire.com

Open Graph data is detected on the main page of Aizen Fire. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Los Angeles Fire Protection & Extinguisher Companies | Fire Extinguishing & Suppression Systems | Ul300, Ansul, Restaurant & Kitchen Hood Services

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

aizenfire.com

aizenfire.com

wp-emoji-release.min.js

custom.css

nivo-lightbox.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

aizenfire.com

aizenfire.com

wp-emoji-release.min.js

custom.css

nivo-lightbox.css

default.css

style.css

css

genericons.css

style.css

js_composer.min.css

formreset.min.css

formsmain.min.css

readyclass.min.css

browsers.min.css

pum-site-styles.css

srpw-frontend.css

n2-ss-2.css

jquery.js

jquery-migrate.min.js

nivo-lightbox.min.js

script.js

jquery.json.min.js

gravityforms.min.js

jquery.maskedinput.min.js

placeholders.jquery.min.js

vertical-m.css

n2.js

nextend-gsap.min.js

nextend-frontend.min.js

smartslider-frontend.min.js

smartslider-simple-type-frontend.min.js

nextend-webfontloader.min.js

css

vc_carousel.min.css

prettyPhoto.min.css

jquery.cycle2.min.js

jquery.cycle2.carousel.js

skip-link-focus-fix.js

api.js

functions.js

core.min.js

position.min.js