Access unify.to. Unify Checkout: Custom eCommerce Checkouts and More!

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value4,790 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

116 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Unify.to and no external sources were called. The less responsive or slowest element that took the longest time to load (116 ms) relates to the external source Codeclouds.com.

Content Size

1.9 MB

After Optimization

1.6 MB

In fact, the total size of Unify.to main page is 1.9 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-20%

Potential reduce by 30 B

Original 151 B
After minification 151 B
After compression 121 B

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 30 B or 20% of the original size.

Image Optimization

-16%

Potential reduce by 291.1 kB

Original 1.8 MB
After minification 1.5 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. Obviously, Unify needs image optimization as it can save up to 291.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 161 B

Original 40.7 kB
After minification 40.7 kB
After compression 40.5 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.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

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 usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA IDs are not unique

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

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

N/A
Encoding

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Unify.to 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 Unify.to main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

unify.to

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