Tools & Wizards About Us
aim.store screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

aim.store

Get Products Directly from Local Producers - aim.store | Regional Food Directly from Local Producer

Page Load Speed

7.6 sec in total

First Response

646 ms

Resources Loaded

5 sec

Page Rendered

2 sec

aim.store screenshot

About Website

Welcome to aim.store homepage info - get ready to check Aim best content right away, or after learning these important things about aim.store

Authentic Regional Food Directly from local Producers Enter your Email and Get a 10% off in your first purchase Enjoy 10% OFF AuthenticRegional Food Directly from local Producers (21) Reviews Pasta e ...

Visit aim.store

Key Findings

We analyzed Aim.store page load time and found that the first response time was 646 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

aim.store performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value4,370 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

aim.store

646 ms

aim.store

545 ms

gtranslate-style16.css

175 ms

woocommerce-multi-currency.min.css

264 ms

styles.css

285 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 68% of them (57 requests) were addressed to the original Aim.store, 6% (5 requests) were made to Google.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Aim.store.

Page Optimization Overview & Recommendations

Page size can be reduced by 307.2 kB (49%)

Content Size

622.2 kB

After Optimization

315.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aim.store main page is 622.2 kB. 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. HTML takes 307.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 256.9 kB

  • Original 307.1 kB
  • After minification 290.8 kB
  • After compression 50.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 256.9 kB or 84% of the original size.

Image Optimization

-10%

Potential reduce by 10.2 kB

  • Original 98.5 kB
  • After minification 88.3 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. Aim images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 39.7 kB

  • Original 154.5 kB
  • After minification 154.4 kB
  • After compression 114.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 39.7 kB or 26% of the original size.

CSS Optimization

-1%

Potential reduce by 466 B

  • Original 62.1 kB
  • After minification 62.1 kB
  • After compression 61.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. Aim.store has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 55 (68%)

Requests Now

81

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aim.store

aim.store

646 ms

aim.store

aim.store

545 ms

gtranslate-style16.css

gtranslate-style16.css

175 ms

woocommerce-multi-currency.min.css

woocommerce-multi-currency.min.css

264 ms

styles.css

styles.css

285 ms

wishlist.css

wishlist.css

280 ms

joinchat-btn.min.css

joinchat-btn.min.css

273 ms

flatsome.css

flatsome.css

358 ms

flatsome-shop.css

flatsome-shop.css

276 ms

mailin-front.css

mailin-front.css

323 ms

css

css

155 ms

jetpack.css

jetpack.css

424 ms

jquery.min.js

jquery.min.js

450 ms

woocommerce-multi-currency.min.js

woocommerce-multi-currency.min.js

350 ms

analytics-talk-content-tracking.js

analytics-talk-content-tracking.js

354 ms

gtm4wp-woocommerce-enhanced.js

gtm4wp-woocommerce-enhanced.js

405 ms

s-202241.js

s-202241.js

153 ms

mailin-front.js

mailin-front.js

448 ms

api.js

api.js

175 ms

js

js

148 ms

index.js

index.js

482 ms

index.js

index.js

482 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

536 ms

add-to-cart.min.js

add-to-cart.min.js

538 ms

js.cookie.min.js

js.cookie.min.js

538 ms

woocommerce.min.js

woocommerce.min.js

580 ms

cart-fragments.min.js

cart-fragments.min.js

580 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

579 ms

wp-polyfill.min.js

wp-polyfill.min.js

579 ms

hoverIntent.min.js

hoverIntent.min.js

577 ms

flatsome.js

flatsome.js

1347 ms

wishlist.js

wishlist.js

1348 ms

flatsome-live-search.js

flatsome-live-search.js

1347 ms

joinchat.min.js

joinchat.min.js

1346 ms

api.js

api.js

132 ms

index.js

index.js

1345 ms

flatsome-lazy-load.js

flatsome-lazy-load.js

1343 ms

woocommerce.js

woocommerce.js

2106 ms

jquery.selectBox.min.js

jquery.selectBox.min.js

2093 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

2093 ms

jquery.yith-wcwl.min.js

jquery.yith-wcwl.min.js

2092 ms

country-select.min.js

country-select.min.js

2091 ms

e-202241.js

e-202241.js

87 ms

shipping-calculater.js

shipping-calculater.js

2090 ms

gtm.js

gtm.js

147 ms

hotjar-3008558.js

hotjar-3008558.js

913 ms

sa.js

sa.js

1671 ms

fbevents.js

fbevents.js

904 ms

spinner.gif

spinner.gif

2248 ms

logo-aimstore-new2.png

logo-aimstore-new2.png

2247 ms

cat-150x150.png

cat-150x150.png

2248 ms

canned-150x150.png

canned-150x150.png

2246 ms

charcuterie-150x150.png

charcuterie-150x150.png

2246 ms

chesse-150x150.png

chesse-150x150.png

2246 ms

delicacies-150x150.png

delicacies-150x150.png

2485 ms

condimets-150x150.png

condimets-150x150.png

2484 ms

pastas-150x150.png

pastas-150x150.png

2484 ms

miel-150x150.png

miel-150x150.png

2484 ms

aceite2-150x150.png

aceite2-150x150.png

2484 ms

vinegars2-150x150.png

vinegars2-150x150.png

2484 ms

box-150x150.png

box-150x150.png

2905 ms

DYI2-150x150.png

DYI2-150x150.png

2906 ms

Plant-icon-150x150.png

Plant-icon-150x150.png

2903 ms

icon-blog-150x150.png

icon-blog-150x150.png

2848 ms

logo-aim-blanco-alfa.png

logo-aim-blanco-alfa.png

2850 ms

fl-icons.ttf

fl-icons.ttf

2810 ms

element.js

element.js

2138 ms

recaptcha__en.js

recaptcha__en.js

2383 ms

conversion_async.js

conversion_async.js

2093 ms

analytics.js

analytics.js

1477 ms

c3po.jpg

c3po.jpg

2082 ms

js

js

709 ms

modules.bcd9ade6b0bb9bdd0789.js

modules.bcd9ade6b0bb9bdd0789.js

1609 ms

identity.js

identity.js

1240 ms

387199032975568

387199032975568

1569 ms

collect

collect

270 ms

825 ms

715 ms

collect

collect

634 ms

chunk.countup.fe2c1016.js

chunk.countup.fe2c1016.js

93 ms

ga-audiences

ga-audiences

54 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

28 ms

21 ms

25 ms

Accessibility Review

aim.store accessibility score

72

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

High

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

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

aim.store 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

aim.store SEO score

84

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

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 Aim.store 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 Aim.store 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

aim.store

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