Tools & Wizards About Us
aemintakes.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

aemintakes.com

AEM Cold Air Intakes & Performance Air Filters

Page Load Speed

1.9 sec in total

First Response

29 ms

Resources Loaded

1.3 sec

Page Rendered

487 ms

aemintakes.com screenshot

About Website

Visit aemintakes.com now to see the best up-to-date AEM Intakes content for United States and also check out these interesting facts you probably never knew about aemintakes.com

Factory direct AEM replacement air filters, and cold air intake systems.

Visit aemintakes.com

Key Findings

We analyzed Aemintakes.com page load time and found that the first response time was 29 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

aemintakes.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value12.1 s

4/100

10%

TBT (Total Blocking Time)

Value3,130 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value21.6 s

1/100

10%

Network Requests Diagram

aemintakes.com

29 ms

aemintakes.com

44 ms

www.aemintakes.com

209 ms

calendar.css

29 ms

styles-m.css

72 ms

Our browser made a total of 160 requests to load all elements on the main page. We found that 82% of them (131 requests) were addressed to the original Aemintakes.com, 6% (10 requests) were made to Res.cloudinary.com and 5% (8 requests) were made to Static.klaviyo.com. The less responsive or slowest element that took the longest time to load (441 ms) belongs to the original domain Aemintakes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 245.5 kB (18%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aemintakes.com main page is 1.3 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. 60% of websites need less resources to load. Images take 887.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 118.0 kB

  • Original 148.3 kB
  • After minification 146.6 kB
  • After compression 30.2 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 118.0 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 15.1 kB

  • Original 887.2 kB
  • After minification 872.1 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. AEM Intakes images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 257 B

  • Original 160.1 kB
  • After minification 160.1 kB
  • After compression 159.8 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

-79%

Potential reduce by 112.2 kB

  • Original 142.5 kB
  • After minification 30.4 kB
  • After compression 30.3 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. Aemintakes.com needs all CSS files to be minified and compressed as it can save up to 112.2 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 132 (87%)

Requests Now

151

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aemintakes.com

aemintakes.com

29 ms

aemintakes.com

aemintakes.com

44 ms

www.aemintakes.com

www.aemintakes.com

209 ms

calendar.css

calendar.css

29 ms

styles-m.css

styles-m.css

72 ms

afterpay-express-checkout.css

afterpay-express-checkout.css

47 ms

main.css

main.css

53 ms

styles-l.css

styles-l.css

63 ms

require.js

require.js

59 ms

disabled.js

disabled.js

55 ms

mixins.js

mixins.js

108 ms

requirejs-config.js

requirejs-config.js

109 ms

banner.js

banner.js

109 ms

css

css

34 ms

css

css

50 ms

wzbody.js

wzbody.js

24 ms

klaviyo.js

klaviyo.js

23 ms

tag.js

tag.js

64 ms

1658860576_1559664499_DSC_0170-drk_1.jpg

1658860576_1559664499_DSC_0170-drk_1.jpg

198 ms

brz.jpg

brz.jpg

182 ms

lc3_9139-min.jpg

lc3_9139-min.jpg

247 ms

dsc_1988-min.jpg

dsc_1988-min.jpg

349 ms

aem_fdirw_2016-min_1.jpg

aem_fdirw_2016-min_1.jpg

362 ms

airfilter.png

airfilter.png

284 ms

cabinairfilter_1.png

cabinairfilter_1.png

334 ms

logo-sm.png

logo-sm.png

337 ms

Type_Color_showSymbol_True_showText_True_ufspsh.png

Type_Color_showSymbol_True_showText_True_ufspsh.png

281 ms

Type_Default_pahnb2.png

Type_Default_pahnb2.png

315 ms

Type_Color_showText_False_showSymbol_True_knzlaw.png

Type_Color_showText_False_showSymbol_True_knzlaw.png

326 ms

logo.svg

logo.svg

48 ms

jquery.js

jquery.js

52 ms

common.js

common.js

44 ms

dataPost.js

dataPost.js

48 ms

bootstrap.js

bootstrap.js

41 ms

app.js

app.js

79 ms

form-key-provider.js

form-key-provider.js

78 ms

mage-translation-dictionary.js

mage-translation-dictionary.js

122 ms

theme.js

theme.js

121 ms

9XUnlJ90n1fBFg7ceXwccVtL.woff

9XUnlJ90n1fBFg7ceXwccVtL.woff

47 ms

9XUilJ90n1fBFg7ceXwUgnhYw5Gt.woff

9XUilJ90n1fBFg7ceXwUgnhYw5Gt.woff

133 ms

9XUilJ90n1fBFg7ceXwUrn9Yw5Gt.woff

9XUilJ90n1fBFg7ceXwUrn9Yw5Gt.woff

134 ms

9XUilJ90n1fBFg7ceXwUyn5Yw5Gt.woff

9XUilJ90n1fBFg7ceXwUyn5Yw5Gt.woff

133 ms

fender_analytics.113876fdc67592e7cbfd.js

fender_analytics.113876fdc67592e7cbfd.js

40 ms

static.047f24ade89e4aff54a9.js

static.047f24ade89e4aff54a9.js

40 ms

runtime.eeee922c197686a9e930.js

runtime.eeee922c197686a9e930.js

20 ms

sharedUtils.00081c57cddd29832b4e.js

sharedUtils.00081c57cddd29832b4e.js

33 ms

vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.b0930143925bb765e2d3.js

vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.b0930143925bb765e2d3.js

30 ms

vendors~signup_forms~onsite-triggering.733ed8744f200f7d4d54.js

vendors~signup_forms~onsite-triggering.733ed8744f200f7d4d54.js

29 ms

vendors~signup_forms.824396622be3ec2234ff.js

vendors~signup_forms.824396622be3ec2234ff.js

27 ms

default~signup_forms~onsite-triggering.968e4cc173bff13b788f.js

default~signup_forms~onsite-triggering.968e4cc173bff13b788f.js

26 ms

signup_forms.3c339f68eee3e750afea.js

signup_forms.3c339f68eee3e750afea.js

29 ms

slick.min.js

slick.min.js

118 ms

accordion.js

accordion.js

116 ms

main.js

main.js

108 ms

main.js

main.js

95 ms

bootstrap.js

bootstrap.js

95 ms

domReady.js

domReady.js

92 ms

jquery-mixin.js

jquery-mixin.js

90 ms

template.js

template.js

86 ms

confirm.js

confirm.js

119 ms

widget.js

widget.js

118 ms

types.js

types.js

41 ms

layout.js

layout.js

41 ms

Luma-Icons.woff

Luma-Icons.woff

126 ms

fontastic.ttf

fontastic.ttf

41 ms

tabs.js

tabs.js

63 ms

smart-keyboard-handler.js

smart-keyboard-handler.js

62 ms

mage.js

mage.js

70 ms

text.js

text.js

68 ms

underscore.js

underscore.js

47 ms

wrapper.js

wrapper.js

67 ms

knockout.js

knockout.js

77 ms

knockout-es5.js

knockout-es5.js

71 ms

scripts.js

scripts.js

65 ms

engine.js

engine.js

74 ms

bootstrap.js

bootstrap.js

79 ms

observable_array.js

observable_array.js

110 ms

bound-nodes.js

bound-nodes.js

102 ms

translate.js

translate.js

87 ms

modal.js

modal.js

99 ms

main.js

main.js

102 ms

registry.js

registry.js

107 ms

version.js

version.js

105 ms

console-logger.js

console-logger.js

103 ms

tabs.js

tabs.js

103 ms

collapsible.js

collapsible.js

105 ms

js-translation.json

js-translation.json

175 ms

observable_source.js

observable_source.js

70 ms

renderer.js

renderer.js

72 ms

knockout-repeat.js

knockout-repeat.js

75 ms

knockout-fast-foreach.js

knockout-fast-foreach.js

83 ms

resizable.js

resizable.js

86 ms

i18n.js

i18n.js

90 ms

scope.js

scope.js

94 ms

range.js

range.js

112 ms

mage-init.js

mage-init.js

108 ms

keyboard.js

keyboard.js

121 ms

optgroup.js

optgroup.js

120 ms

after-render.js

after-render.js

118 ms

autoselect.js

autoselect.js

141 ms

datepicker.js

datepicker.js

140 ms

outer_click.js

outer_click.js

149 ms

fadeVisible.js

fadeVisible.js

141 ms

collapsible.js

collapsible.js

144 ms

staticChecked.js

staticChecked.js

151 ms

simple-checked.js

simple-checked.js

169 ms

bind-html.js

bind-html.js

163 ms

tooltip.js

tooltip.js

164 ms

color-picker.js

color-picker.js

168 ms

events.js

events.js

164 ms

modal-popup.html

modal-popup.html

441 ms

modal-slide.html

modal-slide.html

241 ms

modal-custom.html

modal-custom.html

250 ms

key-codes.js

key-codes.js

187 ms

core.js

core.js

169 ms

z-index.js

z-index.js

193 ms

arrays.js

arrays.js

181 ms

compare.js

compare.js

206 ms

misc.js

misc.js

205 ms

objects.js

objects.js

215 ms

strings.js

strings.js

229 ms

template.js

template.js

225 ms

local.js

local.js

230 ms

logger.js

logger.js

233 ms

entry-factory.js

entry-factory.js

224 ms

console-output-handler.js

console-output-handler.js

223 ms

formatter.js

formatter.js

219 ms

message-pool.js

message-pool.js

246 ms

levels-pool.js

levels-pool.js

231 ms

logger-utils.js

logger-utils.js

221 ms

storage-wrapper.js

storage-wrapper.js

223 ms

keycode.js

keycode.js

212 ms

safe-active-element.js

safe-active-element.js

227 ms

unique-id.js

unique-id.js

240 ms

class.js

class.js

240 ms

loader.js

loader.js

220 ms

async.js

async.js

224 ms

tooltip.html

tooltip.html

274 ms

spectrum.js

spectrum.js

219 ms

tinycolor.js

tinycolor.js

222 ms

data.js

data.js

202 ms

disable-selection.js

disable-selection.js

205 ms

focusable.js

focusable.js

229 ms

form.js

form.js

228 ms

ie.js

ie.js

230 ms

labels.js

labels.js

237 ms

jquery-patch.js

jquery-patch.js

268 ms

plugin.js

plugin.js

249 ms

safe-blur.js

safe-blur.js

244 ms

scroll-parent.js

scroll-parent.js

247 ms

tabbable.js

tabbable.js

228 ms

entry.js

entry.js

191 ms

moment.js

moment.js

182 ms

js.storage.js

js.storage.js

159 ms

dom-observer.js

dom-observer.js

126 ms

bindings.js

bindings.js

126 ms

jquery.cookie.js

jquery.cookie.js

36 ms

cookie-wrapper.js

cookie-wrapper.js

27 ms

js.cookie.js

js.cookie.js

28 ms

print.css

print.css

50 ms

Accessibility Review

aemintakes.com accessibility score

84

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.

ARIA

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.

Impact

Issue

High

ARIA IDs are not unique

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

aemintakes.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

aemintakes.com SEO score

82

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

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

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 Aemintakes.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 Aemintakes.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

aemintakes.com

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