Tools & Wizards About Us

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

invizear.com

The Invisible Hearing Clinic | Glasgow, Scotland.

Page Load Speed

2.8 sec in total

First Response

404 ms

Resources Loaded

2.1 sec

Page Rendered

272 ms

About Website

Welcome to invizear.com homepage info - get ready to check Invizear best content right away, or after learning these important things about invizear.com

The Invisible Hearing Clinic, provides personalised hearing care, Tinnitus support, and advocates for proactive hearing health with a family-inclusive approach.

Visit invizear.com

Key Findings

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

Performance Metrics

invizear.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.609

10/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

invizear.com

404 ms

wpo-minify-header-d6065672.min.css

515 ms

jquery.min.js

606 ms

jquery-migrate.min.js

692 ms

loader.js

41 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 87% of them (27 requests) were addressed to the original Invizear.com, 3% (1 request) were made to Widgets.leadconnectorhq.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (928 ms) belongs to the original domain Invizear.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 208.0 kB (10%)

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Invizear.com main page is 2.0 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. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 129.4 kB

  • Original 157.4 kB
  • After minification 154.6 kB
  • After compression 28.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 129.4 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 77.3 kB

  • 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. Invizear images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

  • Original 351.5 kB
  • After minification 351.5 kB
  • After compression 350.4 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

-1%

Potential reduce by 266 B

  • Original 53.2 kB
  • After minification 53.2 kB
  • After compression 52.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. Invizear.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (59%)

Requests Now

27

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

invizear.com accessibility score

86

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

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

invizear.com SEO score

86

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

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

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