Tools & Wizards About Us
sagecustom.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

sagecustom.com

Sage Custom - Crafted Architectural Products

Page Load Speed

963 ms in total

First Response

59 ms

Resources Loaded

749 ms

Page Rendered

155 ms

sagecustom.com screenshot

About Website

Click here to check amazing Sage Custom content. Otherwise, check out these important facts you probably never knew about sagecustom.com

Crafted Architectural Products…

Visit sagecustom.com

Key Findings

We analyzed Sagecustom.com page load time and found that the first response time was 59 ms and then it took 904 ms 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.

Performance Metrics

sagecustom.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

sagecustom.com

59 ms

style.min.css

23 ms

theme-styles.min.css

31 ms

mkhb-render.min.css

27 ms

mkhb-row.min.css

74 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 49% of them (24 requests) were addressed to the original Sagecustom.com, 35% (17 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (246 ms) belongs to the original domain Sagecustom.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 178.5 kB (34%)

Content Size

517.6 kB

After Optimization

339.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sagecustom.com main page is 517.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. 75% 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. CSS take 221.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 62.0 kB

  • Original 77.8 kB
  • After minification 76.8 kB
  • After compression 15.9 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 62.0 kB or 80% of the original size.

Image Optimization

-16%

Potential reduce by 2.3 kB

  • Original 14.3 kB
  • After minification 12.1 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, Sage Custom needs image optimization as it can save up to 2.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-22%

Potential reduce by 44.3 kB

  • Original 204.5 kB
  • After minification 204.5 kB
  • After compression 160.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 44.3 kB or 22% of the original size.

CSS Optimization

-32%

Potential reduce by 70.0 kB

  • Original 221.0 kB
  • After minification 199.3 kB
  • After compression 151.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. Sagecustom.com needs all CSS files to be minified and compressed as it can save up to 70.0 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (77%)

Requests Now

31

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sagecustom.com

sagecustom.com

59 ms

style.min.css

style.min.css

23 ms

theme-styles.min.css

theme-styles.min.css

31 ms

mkhb-render.min.css

mkhb-render.min.css

27 ms

mkhb-row.min.css

mkhb-row.min.css

74 ms

mkhb-column.min.css

mkhb-column.min.css

25 ms

js_composer.min.css

js_composer.min.css

37 ms

theme-options.min.css

theme-options.min.css

68 ms

shortcodes-styles.min.css

shortcodes-styles.min.css

52 ms

mk-webfontloader.min.js

mk-webfontloader.min.js

70 ms

jquery.min.js

jquery.min.js

69 ms

jquery-migrate.min.js

jquery-migrate.min.js

71 ms

email-decode.min.js

email-decode.min.js

69 ms

css

css

23 ms

smoothscroll.min.js

smoothscroll.min.js

81 ms

core-scripts.min.js

core-scripts.min.js

70 ms

components-full.min.js

components-full.min.js

81 ms

mkhb-render.min.js

mkhb-render.min.js

80 ms

mkhb-column.min.js

mkhb-column.min.js

81 ms

frontend.min.js

frontend.min.js

134 ms

shortcodes-scripts.min.js

shortcodes-scripts.min.js

134 ms

js_composer_front.min.js

js_composer_front.min.js

134 ms

css

css

68 ms

Arcadia-Custom-Logo-Trimmed-new.png

Arcadia-Custom-Logo-Trimmed-new.png

246 ms

sage-custom-90307384.png

sage-custom-90307384.png

232 ms

sage-custom-90307384.js

sage-custom-90307384.js

229 ms

analytics.js

analytics.js

155 ms

Arcadia-Custom-Logo-Trimmed-new-sticky.png

Arcadia-Custom-Logo-Trimmed-new-sticky.png

82 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

108 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

109 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

165 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

174 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

174 ms

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_qiTXtHA_A.ttf

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_qiTXtHA_A.ttf

33 ms

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_pqTXtHA_A.ttf

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_pqTXtHA_A.ttf

75 ms

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_naUXtHA_A.ttf

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_naUXtHA_A.ttf

101 ms

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_k-UXtHA_A.ttf

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_k-UXtHA_A.ttf

102 ms

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_iiUXtHA_A.ttf

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_iiUXtHA_A.ttf

77 ms

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_gGUXtHA_A.ttf

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_gGUXtHA_A.ttf

101 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

100 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf

102 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf

102 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf

103 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf

105 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf

105 ms

jquery.flexslider.js

jquery.flexslider.js

26 ms

collect

collect

42 ms

legacy.min.css

legacy.min.css

46 ms

js

js

59 ms

Accessibility Review

sagecustom.com accessibility score

80

Accessibility Issues

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

sagecustom.com best practices score

83

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

sagecustom.com SEO score

98

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

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

sagecustom.com

Open Graph data is detected on the main page of Sage Custom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: