Access sabinsa.com. Home | Sabinsa Corporation

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value18.0 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

sabinsa.com

206 ms

sabinsa.com

581 ms

simple-line-icons.css

41 ms

k2.css

159 ms

font-awesome.min.css

240 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 92% of them (81 requests) were addressed to the original Sabinsa.com, 1% (1 request) were made to Cdn.jsdelivr.net and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (696 ms) belongs to the original domain Sabinsa.com.

Content Size

165.2 kB

After Optimization

67.4 kB

In fact, the total size of Sabinsa.com main page is 165.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. 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. HTML takes 114.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 97.0 kB

Original 114.8 kB
After minification 107.6 kB
After compression 17.7 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 97.0 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 762 B

Original 50.5 kB
After minification 49.7 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. Sabinsa images are well optimized though.

Requests Now

After Optimization

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

Accessibility Issues

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

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

Form elements do not have associated labels

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

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

High

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

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

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links do not have descriptive text

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

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 Sabinsa.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 Sabinsa.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 Sabinsa. 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: