Access optikam.com. Optikam - Fitting & Dispensing Tool for Eye Care Professionals‎

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value4,290 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.186

66/100

15%

TTI (Time to Interactive)

Value32.1 s

0/100

10%

optikam.com

233 ms

optikam.com

500 ms

js

81 ms

js

136 ms

bootstrap.min.css

343 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 58% of them (42 requests) were addressed to the original Optikam.com, 17% (12 requests) were made to Gstatic.com and 10% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Optikam.com.

Content Size

3.3 MB

After Optimization

2.8 MB

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

HTML Optimization

-62%

Potential reduce by 254.5 kB

Original 410.5 kB
After minification 394.2 kB
After compression 156.0 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 254.5 kB or 62% of the original size.

Image Optimization

-2%

Potential reduce by 52.2 kB

Original 2.1 MB
After minification 2.1 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. Optikam images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 190.9 kB

Original 705.6 kB
After minification 705.6 kB
After compression 514.7 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 190.9 kB or 27% of the original size.

CSS Optimization

-16%

Potential reduce by 7.9 kB

Original 49.5 kB
After minification 49.5 kB
After compression 41.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. Optikam.com needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 16% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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/).

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

optikam.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Optikam - Fitting & Dispensing Tool for Eye Care Professionals‎

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

optikam.com

optikam.com

js

js

bootstrap.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

optikam.com

optikam.com

js

js

bootstrap.min.css

font-awesome.min.css

css

css

css

style-library-1.css

plugins.css

blocks.css

custom.css

btt.css

jquery-2.0.3.min.js

platform.js

loader.js

widget.js

jquery-1.11.1.min.js

bootstrap.min.js

plugins.js

bskit-scripts.js

btt.js

isInViewport.min.js

player.min.js

startup_web.js

846564329

180022939

newlogo.png

Splash5.jpg

iPad_ND.png

iPad_OPD.png

animation3a.gif

Lens%20Package%20-%20White.jpg

animation4a.gif

LD.png

AR.png

int7a.png

Int3a.gif

int6a.png

Int5a.png

Int1a.png

int2a.png