Tools & Wizards About Us
hollisline.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

hollisline.com

Large Part Precision CNC Machining - Prototyping, Pressure Vessels, Vacuum Chambers, Custom Heavy Metal Fabrication | Hollis Line

Page Load Speed

5 sec in total

First Response

1.2 sec

Resources Loaded

3.7 sec

Page Rendered

183 ms

hollisline.com screenshot

About Website

Visit hollisline.com now to see the best up-to-date Hollis Line content and also check out these interesting facts you probably never knew about hollisline.com

Specializing in stainless steel large parts precision CNC machining, protyping, complex fabrication and vbv machining projects.

Visit hollisline.com

Key Findings

We analyzed Hollisline.com page load time and found that the first response time was 1.2 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

hollisline.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.386

27/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

hollisline.com

1156 ms

hollisline.com

1148 ms

js

54 ms

css

28 ms

bootstrap.min.css

76 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 49% of them (19 requests) were addressed to the original Hollisline.com, 36% (14 requests) were made to Fonts.gstatic.com and 8% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Hollisline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 42.8 kB (8%)

Content Size

557.7 kB

After Optimization

514.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 13.6 kB

  • Original 16.7 kB
  • After minification 12.6 kB
  • After compression 3.0 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.1 kB, which is 25% 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 13.6 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 84 B

  • Original 368.9 kB
  • After minification 368.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. Hollis Line images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 11.4 kB

  • Original 90.3 kB
  • After minification 90.3 kB
  • After compression 78.9 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 11.4 kB or 13% of the original size.

CSS Optimization

-22%

Potential reduce by 17.7 kB

  • Original 81.8 kB
  • After minification 81.8 kB
  • After compression 64.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. Hollisline.com needs all CSS files to be minified and compressed as it can save up to 17.7 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (67%)

Requests Now

21

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hollis 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 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hollisline.com

hollisline.com

1156 ms

hollisline.com

hollisline.com

1148 ms

js

js

54 ms

css

css

28 ms

bootstrap.min.css

bootstrap.min.css

76 ms

icofont.min.css

icofont.min.css

149 ms

boxicons.min.css

boxicons.min.css

198 ms

animate.min.css

animate.min.css

202 ms

venobox.css

venobox.css

230 ms

style1.css

style1.css

290 ms

slide-home45.jpg

slide-home45.jpg

425 ms

slide-homelarge-parts.jpg

slide-homelarge-parts.jpg

529 ms

slide-home-proto.jpg

slide-home-proto.jpg

647 ms

spun-weld-home.jpg

spun-weld-home.jpg

797 ms

jquery.min.js

jquery.min.js

859 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

947 ms

jquery.easing.min.js

jquery.easing.min.js

976 ms

jquery.sticky.js

jquery.sticky.js

1058 ms

main.js

main.js

1085 ms

js

js

77 ms

analytics.js

analytics.js

19 ms

js

js

72 ms

collect

collect

60 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

55 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

58 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

62 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

64 ms

icofont.woff

icofont.woff

1009 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

6 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

5 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

13 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

16 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

16 ms

boxicons.woff

boxicons.woff

927 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

23 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

24 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

24 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

24 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

22 ms

Accessibility Review

hollisline.com accessibility score

75

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

hollisline.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

hollisline.com SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

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

hollisline.com

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