Tools & Wizards About Us

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

allergeaze.com

allergEAZE® Allergens & Information for Patch Testing | SmartPractice spcanada

Page Load Speed

1.9 sec in total

First Response

38 ms

Resources Loaded

1.7 sec

Page Rendered

137 ms

About Website

Click here to check amazing AllergEAZE content. Otherwise, check out these important facts you probably never knew about allergeaze.com

Your online resource for a shopping allergEAZE allergens and researching individual allergen information sheets. Visit SmartPractice Canada.

Visit allergeaze.com

Key Findings

We analyzed Allergeaze.com page load time and found that the first response time was 38 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

allergeaze.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.4 s

59/100

10%

Network Requests Diagram

allergeaze.com

38 ms

category

576 ms

jquery.js

124 ms

wicket-ajax-jquery-ver-8FBF37ACEFA139878F1F4590E87D62F8.js

180 ms

SHFocusOutTooltipErrorBehavior-ver-D2A6002091A1A287C9EDF298A2F1F44A.js

179 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Allergeaze.com, 76% (32 requests) were made to Smartpracticecanada.com and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (576 ms) relates to the external source Smartpracticecanada.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 970.5 kB (72%)

Content Size

1.3 MB

After Optimization

374.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Allergeaze.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. 40% of websites need less resources to load. CSS take 660.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 163.0 kB

  • Original 192.4 kB
  • After minification 173.9 kB
  • After compression 29.5 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 163.0 kB or 85% of the original size.

Image Optimization

-73%

Potential reduce by 259.6 kB

  • Original 355.7 kB
  • After minification 96.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. Obviously, AllergEAZE needs image optimization as it can save up to 259.6 kB or 73% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 31.8 kB

  • Original 136.4 kB
  • After minification 131.8 kB
  • After compression 104.6 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 31.8 kB or 23% of the original size.

CSS Optimization

-78%

Potential reduce by 516.1 kB

  • Original 660.8 kB
  • After minification 629.1 kB
  • After compression 144.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. Allergeaze.com needs all CSS files to be minified and compressed as it can save up to 516.1 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (60%)

Requests Now

40

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

allergeaze.com accessibility score

78

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

Form elements do not have associated labels

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.

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

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

allergeaze.com best practices score

75

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

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

High

Page is blocked from indexing

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

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