2.4 sec in total
91 ms
1.1 sec
1.2 sec
Click here to check amazing Libbey content for United States. Otherwise, check out these important facts you probably never knew about libbey.com
What are we celebrating today? Everything that matters to you. We believe every occasion is an opportunity to celebrate life and own the moment.
Visit libbey.comWe analyzed Libbey.com page load time and found that the first response time was 91 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
libbey.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value5.6 s
17/100
25%
Value7.5 s
26/100
10%
Value1,770 ms
10/100
30%
Value0.007
100/100
15%
Value14.1 s
9/100
10%
91 ms
163 ms
104 ms
66 ms
164 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 6% of them (4 requests) were addressed to the original Libbey.com, 73% (46 requests) were made to 3qc4zk1h7fyr3py2kr2wrj0p-wpengine.netdna-ssl.com and 6% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (389 ms) relates to the external source Player.vimeo.com.
Page size can be reduced by 1.2 MB (12%)
10.0 MB
8.8 MB
In fact, the total size of Libbey.com main page is 10.0 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. 80% 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. Images take 8.6 MB which makes up the majority of the site volume.
Potential reduce by 75.8 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 75.8 kB or 84% of the original size.
Potential reduce by 126.3 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. Libbey images are well optimized though.
Potential reduce by 393.3 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 393.3 kB or 66% of the original size.
Potential reduce by 562.4 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. Libbey.com needs all CSS files to be minified and compressed as it can save up to 562.4 kB or 86% of the original size.
Number of requests can be reduced by 31 (53%)
59
28
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Libbey. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
libbey.com
91 ms
libbey.com
163 ms
css
104 ms
stock_widget_style.css
66 ms
css
164 ms
tribe-events-full.min.css
70 ms
grid.css
69 ms
base.css
68 ms
layout.css
74 ms
shortcodes.css
75 ms
magnific-popup.css
69 ms
mediaelementplayer.css
70 ms
enfold.css
81 ms
custom.css
70 ms
event-mod.css
74 ms
jquery.js
83 ms
jquery-migrate.min.js
74 ms
snazzymaps.js
75 ms
call_pipe.js
75 ms
avia-compat.js
78 ms
css
193 ms
avia.js
85 ms
shortcodes.js
85 ms
jquery.magnific-popup.min.js
80 ms
mediaelement-and-player.min.js
84 ms
wp-mediaelement.js
80 ms
wp-embed.min.js
82 ms
wp-emoji-release.min.js
152 ms
tribe-events-full-mobile.min.css
222 ms
analytics.js
238 ms
libbey-logo-new-340.png
190 ms
142166785
389 ms
shop-with-libbey.jpg
142 ms
learn-with-libbey.jpg
143 ms
dine-out-with-libbey.jpg
158 ms
CORP_Product_header1.jpg
142 ms
perfect-signature.jpg
141 ms
ir-laptop.jpg
139 ms
history-1970.jpg
156 ms
Ambiente_2016.jpg
159 ms
libbey_logo_black.png
159 ms
crisa_logo1.png
159 ms
RL_Logo.png
159 ms
Screen-Shot-2015-08-31-at-8.09.26-AM.png
167 ms
Farm-to-Table-Feature.jpg
161 ms
Perfect-Signature-Feature.jpg
161 ms
beSocial-Feature.jpg
161 ms
business-casual-photo.jpg
335 ms
clinking-glasses-705x610.jpg
161 ms
red-car-for-RMK1-705x470.jpg
164 ms
Libbey-HQ-Design-Pic.jpg
163 ms
rss.png
163 ms
wp-emoji-release.min.js
162 ms
entypo-fontello.woff
163 ms
collect
167 ms
player.js
132 ms
player.css
122 ms
ga.js
97 ms
vuid.min.js
78 ms
print.css
16 ms
__utm.gif
62 ms
proxy.html
26 ms
539381912.jpg
60 ms
libbey.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
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.
Impact
Issue
Links do not have a discernible name
libbey.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
libbey.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
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/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Libbey.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 Libbey.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.
libbey.com
Open Graph data is detected on the main page of Libbey. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: