Tools & Wizards About Us
gramor.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

gramor.com

Gramor Development | Commercial Real Estate Development | Portland OR | Vancouver WA

Page Load Speed

1.7 sec in total

First Response

135 ms

Resources Loaded

1.4 sec

Page Rendered

111 ms

gramor.com screenshot

About Website

Click here to check amazing Gramor content. Otherwise, check out these important facts you probably never knew about gramor.com

Gramor Development is a commercial real estate development company focused on the Portland OR and Vancouver WA area.

Visit gramor.com

Key Findings

We analyzed Gramor.com page load time and found that the first response time was 135 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

gramor.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value4.4 s

75/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

www.gramor.com

135 ms

minified.js

93 ms

focus-within-polyfill.js

156 ms

polyfill.min.js

164 ms

thunderbolt-commons.7700cd07.bundle.min.js

127 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Gramor.com, 37% (20 requests) were made to Static.wixstatic.com and 35% (19 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (764 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 406.6 kB (16%)

Content Size

2.5 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Gramor.com main page is 2.5 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. 65% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 393.6 kB

  • Original 510.0 kB
  • After minification 508.2 kB
  • After compression 116.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. 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 393.6 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 3.8 kB

  • Original 1.8 MB
  • After minification 1.8 MB

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. Gramor images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 9.3 kB

  • Original 264.7 kB
  • After minification 264.7 kB
  • After compression 255.4 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.

Requests Breakdown

Number of requests can be reduced by 10 (29%)

Requests Now

35

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.gramor.com

www.gramor.com

135 ms

minified.js

minified.js

93 ms

focus-within-polyfill.js

focus-within-polyfill.js

156 ms

polyfill.min.js

polyfill.min.js

164 ms

thunderbolt-commons.7700cd07.bundle.min.js

thunderbolt-commons.7700cd07.bundle.min.js

127 ms

main.16c08821.bundle.min.js

main.16c08821.bundle.min.js

127 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

126 ms

lodash.min.js

lodash.min.js

126 ms

react.production.min.js

react.production.min.js

125 ms

react-dom.production.min.js

react-dom.production.min.js

127 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

220 ms

e0b585_f6d98d6ed35a4fe89023f1eff97fbd2d~mv2.png

e0b585_f6d98d6ed35a4fe89023f1eff97fbd2d~mv2.png

287 ms

bundle.min.js

bundle.min.js

154 ms

51b0f9_35f139c637e8414b9acb618480812fd4f000.jpg

51b0f9_35f139c637e8414b9acb618480812fd4f000.jpg

228 ms

e0b585_f6d98d6ed35a4fe89023f1eff97fbd2d~mv2.png

e0b585_f6d98d6ed35a4fe89023f1eff97fbd2d~mv2.png

215 ms

51b0f9_3aec05cbacda4cc8a3262a30ef05ca55~mv2.jpg

51b0f9_3aec05cbacda4cc8a3262a30ef05ca55~mv2.jpg

214 ms

e0b585_1fb08b38ecb2416ca2ed2aa0dea0d69d~mv2.jpg

e0b585_1fb08b38ecb2416ca2ed2aa0dea0d69d~mv2.jpg

244 ms

51b0f9_d54d11405c844498b13e0c67e4135dfa~mv2.jpg

51b0f9_d54d11405c844498b13e0c67e4135dfa~mv2.jpg

257 ms

e0b585_33a96c940f2a41e7a546491d620d5228~mv2.jpg

e0b585_33a96c940f2a41e7a546491d620d5228~mv2.jpg

384 ms

51b0f9_3c72f483b1f04834ab4e8d31f23fed3b~mv2.jpg

51b0f9_3c72f483b1f04834ab4e8d31f23fed3b~mv2.jpg

451 ms

51b0f9_0ef30c462bf74596b58df49ed4982215~mv2.jpg

51b0f9_0ef30c462bf74596b58df49ed4982215~mv2.jpg

547 ms

e0b585_68b7d77428984478abfed3f5b8cf4459~mv2.jpg

e0b585_68b7d77428984478abfed3f5b8cf4459~mv2.jpg

410 ms

51b0f9_a2a2bea218474f78bbb9e797fa7bc0f0~mv2.jpg

51b0f9_a2a2bea218474f78bbb9e797fa7bc0f0~mv2.jpg

356 ms

e0b585_3ed7c985dd5a4dc7bcbf5f77778c0b23~mv2.jpg

e0b585_3ed7c985dd5a4dc7bcbf5f77778c0b23~mv2.jpg

410 ms

51b0f9_6009ae51888744c191dd4bbf006449fb~mv2.jpg

51b0f9_6009ae51888744c191dd4bbf006449fb~mv2.jpg

554 ms

51b0f9_f69ee5a27e4f41e4a18e211f14c585f2~mv2.jpg

51b0f9_f69ee5a27e4f41e4a18e211f14c585f2~mv2.jpg

592 ms

e0b585_eb6c3dd9609947fa8cdfde835ac84966~mv2.jpg

e0b585_eb6c3dd9609947fa8cdfde835ac84966~mv2.jpg

591 ms

51b0f9_690107dd5b394892a22e6857cfda69bd~mv2.jpg

51b0f9_690107dd5b394892a22e6857cfda69bd~mv2.jpg

564 ms

51b0f9_c6b3ecbe0a2f495d971a70a2ea54d5db~mv2.jpg

51b0f9_c6b3ecbe0a2f495d971a70a2ea54d5db~mv2.jpg

645 ms

e0b585_17b048929c784cfb92a5340863dbc777~mv2.jpg

e0b585_17b048929c784cfb92a5340863dbc777~mv2.jpg

764 ms

e0b585_b6d667728add478ca660d92b5325aee2~mv2.jpg

e0b585_b6d667728add478ca660d92b5325aee2~mv2.jpg

701 ms

e0b585_f6d98d6ed35a4fe89023f1eff97fbd2d~mv2.png

e0b585_f6d98d6ed35a4fe89023f1eff97fbd2d~mv2.png

674 ms

388ef902-2c31-4818-abb1-a40dcd81f6d6.woff

388ef902-2c31-4818-abb1-a40dcd81f6d6.woff

11 ms

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

11 ms

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

11 ms

AvenirLTW05-35Light.woff

AvenirLTW05-35Light.woff

16 ms

125 ms

118 ms

131 ms

118 ms

126 ms

122 ms

153 ms

147 ms

149 ms

162 ms

156 ms

deprecation-en.v5.html

deprecation-en.v5.html

6 ms

bolt-performance

bolt-performance

73 ms

deprecation-style.v5.css

deprecation-style.v5.css

31 ms

right-arrow.svg

right-arrow.svg

65 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

9 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

9 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

10 ms

Accessibility Review

gramor.com accessibility score

96

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.

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

gramor.com 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

Page has valid source maps

SEO Factors

gramor.com SEO score

99

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

gramor.com

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