Tools & Wizards About Us
quarry.team screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

quarry.team

Digital Products That Satisfy, Empower, & Convert | Quarry

Page Load Speed

800 ms in total

First Response

28 ms

Resources Loaded

400 ms

Page Rendered

372 ms

quarry.team screenshot

About Website

Click here to check amazing Quarry content. Otherwise, check out these important facts you probably never knew about quarry.team

Quarry is a full-stack web products team that crafts high-converting solutions through strategy, design, & engineering. Offices in Medford, OR.

Visit quarry.team

Key Findings

We analyzed Quarry.team page load time and found that the first response time was 28 ms and then it took 772 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

quarry.team performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value3.8 s

85/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

quarry.team

28 ms

quarry.team

44 ms

css

53 ms

css

63 ms

2.styles.0cc66322.css

28 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 47% of them (14 requests) were addressed to the original Quarry.team, 47% (14 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (89 ms) belongs to the original domain Quarry.team.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.1 kB (7%)

Content Size

378.6 kB

After Optimization

350.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Quarry.team main page is 378.6 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. 65% of websites need less resources to load. Javascripts take 272.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 28.0 kB

  • Original 36.3 kB
  • After minification 35.7 kB
  • After compression 8.3 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 28.0 kB or 77% of the original size.

JavaScript Optimization

-0%

Potential reduce by 133 B

  • Original 272.2 kB
  • After minification 272.2 kB
  • After compression 272.1 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

-0%

Potential reduce by 0 B

  • Original 70.0 kB
  • After minification 70.0 kB
  • After compression 70.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. Quarry.team has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (36%)

Requests Now

14

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

quarry.team

quarry.team

28 ms

quarry.team

quarry.team

44 ms

css

css

53 ms

css

css

63 ms

2.styles.0cc66322.css

2.styles.0cc66322.css

28 ms

app.43aa1586.js

app.43aa1586.js

89 ms

page--src--pages--index-vue.39dde588.js

page--src--pages--index-vue.39dde588.js

54 ms

page--src--pages--contact-vue~page--src--pages--index-vue~page--src--pages--privacy-policy-vue~page-~a0ac4265.bf80164e.js

page--src--pages--contact-vue~page--src--pages--index-vue~page--src--pages--privacy-policy-vue~page-~a0ac4265.bf80164e.js

52 ms

icon-logo-quarry.0800e850.svg

icon-logo-quarry.0800e850.svg

51 ms

1ftp_BusinessMember_Horizontal_Black.193ad116.svg

1ftp_BusinessMember_Horizontal_Black.193ad116.svg

49 ms

icon-partner-oregon.381f1b68.svg

icon-partner-oregon.381f1b68.svg

55 ms

icon-partner-global-elite.85a31d00.svg

icon-partner-global-elite.85a31d00.svg

75 ms

icon-partner-shopify.4a347d43.svg

icon-partner-shopify.4a347d43.svg

53 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFlOl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFlOl0k30e0.ttf

19 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFlnl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFlnl0k30e0.ttf

31 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

61 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k30e0.ttf

74 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFn8kEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFn8kEk30e0.ttf

76 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf

76 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e0.ttf

75 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

75 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

74 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

76 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

77 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

77 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

77 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

78 ms

page--node-modules--gridsome--app--pages--404-vue.9000a58d.js

page--node-modules--gridsome--app--pages--404-vue.9000a58d.js

13 ms

page--src--pages--blog-vue.8dd75efe.js

page--src--pages--blog-vue.8dd75efe.js

47 ms

page--src--pages--case-detail-vue.5345bffb.js

page--src--pages--case-detail-vue.5345bffb.js

57 ms

Accessibility Review

quarry.team accessibility score

68

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

button, link, and menuitem elements 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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

quarry.team best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

quarry.team SEO score

90

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

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

High

Tap targets are not sized appropriately

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 Quarry.team 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 Quarry.team 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

quarry.team

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