Tools & Wizards About Us
aspartame.net screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

aspartame.net

Aspartame - Amino Acid-Based Sweetener | Ajinomoto Health & Nutrition

Page Load Speed

1.9 sec in total

First Response

63 ms

Resources Loaded

1.3 sec

Page Rendered

539 ms

aspartame.net screenshot

About Website

Visit aspartame.net now to see the best up-to-date Aspartame content for United States and also check out these interesting facts you probably never knew about aspartame.net

The world's best high potency amino acid-based sweetener for sugar-like taste. Made of amino acids found naturally in fruits & vegetables. Order a sample!

Visit aspartame.net

Key Findings

We analyzed Aspartame.net page load time and found that the first response time was 63 ms and then it took 1.9 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

aspartame.net performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

aspartame.net

63 ms

206 ms

theme.min.css

60 ms

style.css

89 ms

frontend.css

94 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Aspartame.net, 96% (97 requests) were made to Ajihealthandnutrition.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (617 ms) relates to the external source Ajihealthandnutrition.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.5 kB (11%)

Content Size

2.5 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aspartame.net main page is 2.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 204.6 kB

  • Original 235.2 kB
  • After minification 230.4 kB
  • After compression 30.6 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 204.6 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 57.1 kB

  • Original 1.7 MB
  • After minification 1.7 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. Aspartame images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.5 kB

  • Original 292.6 kB
  • After minification 292.6 kB
  • After compression 289.1 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

-4%

Potential reduce by 8.4 kB

  • Original 204.5 kB
  • After minification 204.5 kB
  • After compression 196.1 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. Aspartame.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 75 (80%)

Requests Now

94

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aspartame.net

aspartame.net

63 ms

206 ms

theme.min.css

theme.min.css

60 ms

style.css

style.css

89 ms

frontend.css

frontend.css

94 ms

style.min.css

style.min.css

96 ms

frontend.min.css

frontend.min.css

132 ms

post-5.css

post-5.css

90 ms

animations.min.css

animations.min.css

96 ms

style.css

style.css

117 ms

header-footer.min.css

header-footer.min.css

122 ms

all.min.css

all.min.css

136 ms

v4-shims.min.css

v4-shims.min.css

122 ms

public.css

public.css

126 ms

jet-popup-frontend.css

jet-popup-frontend.css

147 ms

custom-jet-blocks.css

custom-jet-blocks.css

155 ms

jet-elements.css

jet-elements.css

169 ms

jet-elements-skin.css

jet-elements-skin.css

159 ms

elementor-icons.min.css

elementor-icons.min.css

160 ms

swiper.min.css

swiper.min.css

160 ms

frontend.min.css

frontend.min.css

224 ms

jet-blog.css

jet-blog.css

195 ms

jet-tabs-frontend.css

jet-tabs-frontend.css

194 ms

jet-tricks-frontend.css

jet-tricks-frontend.css

191 ms

post-7388.css

post-7388.css

204 ms

post-187.css

post-187.css

200 ms

post-254.css

post-254.css

237 ms

chosen.min.css

chosen.min.css

238 ms

jet-search.css

jet-search.css

240 ms

fontawesome.min.css

fontawesome.min.css

245 ms

solid.min.css

solid.min.css

243 ms

brands.min.css

brands.min.css

252 ms

jquery.min.js

jquery.min.js

274 ms

jquery-migrate.min.js

jquery-migrate.min.js

260 ms

imagesloaded.min.js

imagesloaded.min.js

260 ms

script.js

script.js

263 ms

js

js

58 ms

post-7175.css

post-7175.css

246 ms

post-2672.css

post-2672.css

353 ms

post-12680.css

post-12680.css

323 ms

post-4357.css

post-4357.css

296 ms

post-4324.css

post-4324.css

293 ms

underscore.min.js

underscore.min.js

291 ms

wp-util.min.js

wp-util.min.js

289 ms

chosen.jquery.min.js

chosen.jquery.min.js

290 ms

jet-plugins.js

jet-plugins.js

271 ms

jet-search.js

jet-search.js

266 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

265 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

260 ms

wp-polyfill.min.js

wp-polyfill.min.js

252 ms

hooks.min.js

hooks.min.js

253 ms

vue.min.js

vue.min.js

347 ms

jet-menu-public-scripts.js

jet-menu-public-scripts.js

236 ms

anime.min.js

anime.min.js

233 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

232 ms

jet-popup-frontend.js

jet-popup-frontend.js

332 ms

seopress-cookies.min.js

seopress-cookies.min.js

315 ms

seopress-cookies-ajax.min.js

seopress-cookies-ajax.min.js

301 ms

dwf.js

dwf.js

294 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

295 ms

hoverIntent.min.js

hoverIntent.min.js

294 ms

frontend.js

frontend.js

291 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

260 ms

webpack.runtime.min.js

webpack.runtime.min.js

257 ms

frontend-modules.min.js

frontend-modules.min.js

254 ms

i18n.min.js

i18n.min.js

252 ms

frontend.min.js

frontend.min.js

253 ms

waypoints.min.js

waypoints.min.js

251 ms

core.min.js

core.min.js

238 ms

frontend.min.js

frontend.min.js

237 ms

elements-handlers.min.js

elements-handlers.min.js

238 ms

jet-blocks.min.js

jet-blocks.min.js

236 ms

jet-elements.min.js

jet-elements.min.js

235 ms

widgets-scripts.js

widgets-scripts.js

125 ms

jet-popup-elementor-frontend.js

jet-popup-elementor-frontend.js

125 ms

jet-tabs-frontend.min.js

jet-tabs-frontend.min.js

171 ms

jet-tricks-frontend.js

jet-tricks-frontend.js

171 ms

jet-blog.min.js

jet-blog.min.js

170 ms

ajinomoto_globe.png

ajinomoto_globe.png

170 ms

logo_aj-final.svg

logo_aj-final.svg

170 ms

intro_image-large_aspartame.jpg

intro_image-large_aspartame.jpg

270 ms

intro_image-small_aspartame.jpg

intro_image-small_aspartame.jpg

268 ms

Site-Icons_T10-Low-Calorie-Aspartame-150x150.png

Site-Icons_T10-Low-Calorie-Aspartame-150x150.png

267 ms

Site-Icons_T9-Sugar-Reduction-Beverages-150x150.png

Site-Icons_T9-Sugar-Reduction-Beverages-150x150.png

265 ms

Site-Icons_T10-Amino-Acids-Fruit-Aspartame-150x150.png

Site-Icons_T10-Amino-Acids-Fruit-Aspartame-150x150.png

334 ms

soda-686984_1920.jpg

soda-686984_1920.jpg

617 ms

sorin-popa-F6zJEnVv6to-unsplash-scaled.jpg

sorin-popa-F6zJEnVv6to-unsplash-scaled.jpg

437 ms

1-11.jpg

1-11.jpg

264 ms

2-17.jpg

2-17.jpg

261 ms

food_beverage-confectionary-Industry-Application-Image.jpg

food_beverage-confectionary-Industry-Application-Image.jpg

230 ms

3-12.jpg

3-12.jpg

228 ms

sauces_dressing-Industry-Application-Image.jpg

sauces_dressing-Industry-Application-Image.jpg

284 ms

iStock_000017238606_Full-scaled.jpg

iStock_000017238606_Full-scaled.jpg

514 ms

fa-solid-900.woff

fa-solid-900.woff

408 ms

fa-solid-900.woff

fa-solid-900.woff

363 ms

fa-regular-400.woff

fa-regular-400.woff

320 ms

shutterstock_1791855119-scaled.jpg

shutterstock_1791855119-scaled.jpg

400 ms

fa-brands-400.woff

fa-brands-400.woff

397 ms

fa-brands-400.woff

fa-brands-400.woff

398 ms

insight.min.js

insight.min.js

59 ms

insight_tag_errors.gif

insight_tag_errors.gif

144 ms

Accessibility Review

aspartame.net accessibility score

87

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

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

Best Practices

aspartame.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

aspartame.net SEO score

83

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 Aspartame.net 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 Aspartame.net 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

aspartame.net

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