1.4 sec in total
339 ms
882 ms
198 ms
Click here to check amazing Glass Eye content for United States. Otherwise, check out these important facts you probably never knew about glasseye.com
Handblown glass art, gifts, and collectibles made by artisan glassblowers in our Seattle studio since 1978.
Visit glasseye.comWe analyzed Glasseye.com page load time and found that the first response time was 339 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster. This domain responded with an error, which can significantly jeopardize Glasseye.com rating and web reputation
glasseye.com performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value14.3 s
0/100
25%
Value5.2 s
59/100
10%
Value1,800 ms
10/100
30%
Value0.001
100/100
15%
Value14.3 s
9/100
10%
339 ms
55 ms
80 ms
16 ms
16 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Glasseye.com, 50% (36 requests) were made to Cdn4.bigcommerce.com and 31% (22 requests) were made to Cdn3.bigcommerce.com. The less responsive or slowest element that took the longest time to load (339 ms) belongs to the original domain Glasseye.com.
Page size can be reduced by 345.6 kB (18%)
1.9 MB
1.6 MB
In fact, the total size of Glasseye.com main page is 1.9 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 35.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. This page needs HTML code to be minified as it can gain 5.0 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 35.8 kB or 83% of the original size.
Potential reduce by 8.9 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. Glass Eye images are well optimized though.
Potential reduce by 229.7 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 229.7 kB or 72% of the original size.
Potential reduce by 71.1 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. Glasseye.com needs all CSS files to be minified and compressed as it can save up to 71.1 kB or 81% of the original size.
Number of requests can be reduced by 47 (72%)
65
18
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Glass Eye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
glasseye.com
339 ms
css
55 ms
css
80 ms
styles.css
16 ms
iselector.css
16 ms
flexslider.css
16 ms
slide-show.css
19 ms
styles-slide-show.css
18 ms
social.css
17 ms
styles.css
48 ms
Light.css
62 ms
theme.css
46 ms
grid.css
46 ms
responsive.css
46 ms
font-awesome.css
61 ms
custom.css
70 ms
product.attributes.css
67 ms
ui.all.css
67 ms
product.quickview.css
66 ms
imodal.css
70 ms
store.css
62 ms
jquery.min.js
109 ms
menudrop.js
44 ms
iselector.js
45 ms
jquery.flexslider.js
59 ms
viewport.js
59 ms
matchMedia.js
60 ms
common.js
60 ms
jquery.autobox.js
66 ms
init.js
62 ms
jquery.uniform.min.js
68 ms
main.js
68 ms
jquery-ui.min.js
131 ms
quickview.js
66 ms
jquery.form.js
69 ms
imodal.js
69 ms
quicksearch.js
68 ms
jquery.bgiframe.min.js
66 ms
superfish.js
67 ms
visitor.js
68 ms
css
19 ms
home-slideshow.css
16 ms
analytics.js
5 ms
collect
16 ms
analytics.min.js
104 ms
collect
145 ms
beacon_api.js
76 ms
bgBody.jpg
76 ms
index.php
324 ms
loader.png
39 ms
icon-cart.png
40 ms
logo.png
49 ms
searchIcon.png
43 ms
bgLeftColGreen.jpg
43 ms
btmCatSwirl.png
43 ms
GES_A102_Rune_VIolet_web__08894.1432749158.165.285.jpg
81 ms
IcoRating0.png
48 ms
GES_620_Winter_Wonderland_N4__90229.1450480123.165.285.jpg
50 ms
GES_OG161_Tuxedo_web__35269.1432747041.165.285.jpg
82 ms
GES_617_Waterspout_72__95181__58142.1421355619.165.285.jpg
49 ms
1.jpg
133 ms
2.jpg
98 ms
3.jpg
98 ms
4.jpg
82 ms
5.jpg
101 ms
sprite-social.png
41 ms
arrows-ffffff.png
47 ms
Hm1qjDlZpOdVXoa-QGE7_w.ttf
34 ms
L74890HNVnUypqWjqGUt1aCWcynf_cDxXwCLxiixG1c.ttf
41 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
43 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
43 ms
fornax.min.js
54 ms
glasseye.com accessibility score
ARIA
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.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
glasseye.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
glasseye.com SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Glasseye.com 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 Glasseye.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.
glasseye.com
Open Graph description is not detected on the main page of Glass Eye. 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: