Tools & Wizards About Us
glassline.net screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

glassline.net

GLASS LINE Magazine... Flameworking

Page Load Speed

2.9 sec in total

First Response

773 ms

Resources Loaded

2.1 sec

Page Rendered

72 ms

glassline.net screenshot

About Website

Welcome to glassline.net homepage info - get ready to check GLASS LINE best content for United States right away, or after learning these important things about glassline.net

The world's only publication entirely devoted to GlassBlowing - LampWorking - FlameWorked - HOT GLASS Art & Artists...... is now on line! Check it out!

Visit glassline.net

Key Findings

We analyzed Glassline.net page load time and found that the first response time was 773 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

glassline.net performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

93/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

glassline.net

773 ms

backissues.css

433 ms

magicslideshow.css

71 ms

magicslideshow.js

195 ms

urchin.js

21 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 15% of them (7 requests) were addressed to the original Glassline.net, 70% (32 requests) were made to Flameworkers.com and 7% (3 requests) were made to Hotglass.com. The less responsive or slowest element that took the longest time to load (840 ms) belongs to the original domain Glassline.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (71%)

Content Size

1.7 MB

After Optimization

476.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Glassline.net main page is 1.7 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. 25% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 16.4 kB

  • Original 20.9 kB
  • After minification 16.7 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 4.2 kB, which is 20% 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 16.4 kB or 78% of the original size.

Image Optimization

-76%

Potential reduce by 1.2 MB

  • Original 1.5 MB
  • After minification 366.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, GLASS LINE needs image optimization as it can save up to 1.2 MB or 76% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 2.7 kB

  • Original 107.1 kB
  • After minification 107.1 kB
  • After compression 104.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. This website has mostly compressed JavaScripts.

CSS Optimization

-64%

Potential reduce by 2.1 kB

  • Original 3.3 kB
  • After minification 2.5 kB
  • After compression 1.2 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. Glassline.net needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (7%)

Requests Now

44

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

glassline.net

glassline.net

773 ms

backissues.css

backissues.css

433 ms

magicslideshow.css

magicslideshow.css

71 ms

magicslideshow.js

magicslideshow.js

195 ms

urchin.js

urchin.js

21 ms

__utm.gif

__utm.gif

26 ms

plusone.js

plusone.js

33 ms

logo-10_sm.png

logo-10_sm.png

840 ms

hr1.gif

hr1.gif

66 ms

1.jpg

1.jpg

436 ms

22.jpg

22.jpg

450 ms

23.jpg

23.jpg

454 ms

20.jpg

20.jpg

478 ms

19.jpg

19.jpg

479 ms

18.jpg

18.jpg

479 ms

21.jpg

21.jpg

498 ms

2.jpg

2.jpg

511 ms

3.jpg

3.jpg

517 ms

4.jpg

4.jpg

540 ms

6.jpg

6.jpg

541 ms

7.jpg

7.jpg

541 ms

8.jpg

8.jpg

560 ms

9.jpg

9.jpg

573 ms

10.jpg

10.jpg

578 ms

11.jpg

11.jpg

608 ms

12.jpg

12.jpg

608 ms

13.jpg

13.jpg

609 ms

14.jpg

14.jpg

623 ms

15.jpg

15.jpg

636 ms

16.jpg

16.jpg

640 ms

17.jpg

17.jpg

666 ms

Charlie_Sanford.jpg

Charlie_Sanford.jpg

671 ms

Leah_Fairbanks.jpg

Leah_Fairbanks.jpg

671 ms

Bashi_Ale.jpg

Bashi_Ale.jpg

688 ms

Melanie_Moertel.jpg

Melanie_Moertel.jpg

701 ms

Eric_Edner.jpg

Eric_Edner.jpg

703 ms

Matt_Entenmann.jpg

Matt_Entenmann.jpg

732 ms

Voicu_Florin1.jpg

Voicu_Florin1.jpg

736 ms

Mike_Nelson.jpg

Mike_Nelson.jpg

737 ms

Akiko_Shinoda.jpg

Akiko_Shinoda.jpg

751 ms

mb-1.gif

mb-1.gif

69 ms

Cover_v28n1-med.jpg

Cover_v28n1-med.jpg

601 ms

ajs.php

ajs.php

755 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

arrows06.png

arrows06.png

66 ms

loader.gif

loader.gif

64 ms

Accessibility Review

glassline.net accessibility score

61

Accessibility Issues

Internationalization and localization

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

Impact

Issue

High

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

glassline.net best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

glassline.net SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Glassline.net 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 Glassline.net 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

glassline.net

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