Access hoppify.com. Hoppify

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

hoppify.com

29 ms

css

22 ms

welcomebg1.png

18 ms

S6u8w4BMUTPHh30AXC-v.ttf

10 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

15 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 40% of them (2 requests) were addressed to the original Hoppify.com, 40% (2 requests) were made to Fonts.gstatic.com and 20% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (29 ms) belongs to the original domain Hoppify.com.

Content Size

575.6 kB

After Optimization

532.7 kB

In fact, the total size of Hoppify.com main page is 575.6 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. 15% of websites need less resources to load. Images take 574.0 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 1.1 kB

Original 1.6 kB
After minification 1.5 kB
After compression 514 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 1.1 kB or 68% of the original size.

Image Optimization

-7%

Potential reduce by 41.8 kB

Original 574.0 kB
After minification 532.2 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. Hoppify images are well optimized though.

Requests Now

After Optimization

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hoppify. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Search Engine Optimization Advices

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

High

robots.txt is not valid

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hoppify.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Hoppify.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 Hoppify. 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: