Tools & Wizards About Us
enesco.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

enesco.com

Enesco, LLC – Enesco Corporate Website

Page Load Speed

844 ms in total

First Response

211 ms

Resources Loaded

525 ms

Page Rendered

108 ms

enesco.com screenshot

About Website

Click here to check amazing Enesco content for United States. Otherwise, check out these important facts you probably never knew about enesco.com

Learn about Enesco Gift, Department 56, Gund, Gregg Gift Company. Unwrap the Magic and Experience a Brand New World of Enesco Collectibles and Figurines

Visit enesco.com

Key Findings

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

Performance Metrics

enesco.com performance score

0

Network Requests Diagram

enesco.com

211 ms

css

38 ms

css

61 ms

global.css

123 ms

font-awesome.min.css

90 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 66% of them (21 requests) were addressed to the original Enesco.com, 13% (4 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (211 ms) belongs to the original domain Enesco.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 180.6 kB (63%)

Content Size

287.0 kB

After Optimization

106.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Enesco.com main page is 287.0 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. 25% of websites need less resources to load. Javascripts take 117.9 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 16.7 kB

  • Original 24.2 kB
  • After minification 22.9 kB
  • After compression 7.5 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 16.7 kB or 69% of the original size.

Image Optimization

-11%

Potential reduce by 5.8 kB

  • Original 51.7 kB
  • After minification 45.8 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. Obviously, Enesco needs image optimization as it can save up to 5.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 78.9 kB

  • Original 117.9 kB
  • After minification 91.3 kB
  • After compression 39.0 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 78.9 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 79.2 kB

  • Original 93.2 kB
  • After minification 75.1 kB
  • After compression 14.0 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. Enesco.com needs all CSS files to be minified and compressed as it can save up to 79.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (38%)

Requests Now

26

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

enesco.com

enesco.com

211 ms

css

css

38 ms

css

css

61 ms

global.css

global.css

123 ms

font-awesome.min.css

font-awesome.min.css

90 ms

jquery-latest.min.js

jquery-latest.min.js

4 ms

swfobject_modified.js

swfobject_modified.js

33 ms

jquery.hoverIntent.js

jquery.hoverIntent.js

97 ms

jquery.cluetip.js

jquery.cluetip.js

118 ms

scrolltop.js

scrolltop.js

63 ms

message.js

message.js

183 ms

enesco_logo_verticle.jpg

enesco_logo_verticle.jpg

33 ms

us_flag.gif

us_flag.gif

31 ms

fr_flag.gif

fr_flag.gif

31 ms

ca_flag.gif

ca_flag.gif

32 ms

uk_flag.gif

uk_flag.gif

34 ms

enesco-b2c-callout.jpg

enesco-b2c-callout.jpg

100 ms

callout5_NewsEvents.jpg

callout5_NewsEvents.jpg

98 ms

middot.jpg

middot.jpg

98 ms

enesco-logo-facebook.jpg

enesco-logo-facebook.jpg

97 ms

enesco-gift-logo-facebook.jpg

enesco-gift-logo-facebook.jpg

96 ms

gund-logo-facebook.jpg

gund-logo-facebook.jpg

98 ms

department56-logo-facebook.jpg

department56-logo-facebook.jpg

101 ms

analytics.js

analytics.js

20 ms

collect

collect

15 ms

up.png

up.png

31 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

31 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

43 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

57 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

63 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

93 ms

nr-536.min.js

nr-536.min.js

17 ms

SEO Factors

enesco.com SEO score

0

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

enesco.com

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