3.7 sec in total
313 ms
2.6 sec
794 ms
Visit satchelpdx.com now to see the best up-to-date Satchel Pdx content for Canada and also check out these interesting facts you probably never knew about satchelpdx.com
Portland dispensary Satchel OLCC licensed Rec/Med provider serving the best that Oregon has to offer. Check out our dispensary Menu page.
Visit satchelpdx.comWe analyzed Satchelpdx.com page load time and found that the first response time was 313 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
satchelpdx.com performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value5.5 s
19/100
25%
Value8.2 s
20/100
10%
Value1,400 ms
16/100
30%
Value0.023
100/100
15%
Value7.1 s
52/100
10%
313 ms
184 ms
322 ms
69 ms
256 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 33% of them (10 requests) were addressed to the original Satchelpdx.com, 50% (15 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (491 ms) belongs to the original domain Satchelpdx.com.
Page size can be reduced by 21.9 kB (19%)
118.1 kB
96.2 kB
In fact, the total size of Satchelpdx.com main page is 118.1 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. 50% of websites need less resources to load. CSS take 34.3 kB which makes up the majority of the site volume.
Potential reduce by 21.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 21.3 kB or 75% of the original size.
Potential reduce by 0 B
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. Satchel Pdx images are well optimized though.
Potential reduce by 76 B
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.
Potential reduce by 509 B
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. Satchelpdx.com has all CSS files already compressed.
Number of requests can be reduced by 5 (42%)
12
7
The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Satchel Pdx. 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.
satchelpdx.com
313 ms
072e191b711871b904522d45ad7d5f90-compressor-part.css
184 ms
213b664ff7bc60e8954c0222a4cfa90d-compressor-part.js
322 ms
js
69 ms
f0ce8daaca6faf2bc852ba78936f9fff-compressor-part.js
256 ms
5c232b0abeadad413adec51e98f8bf0d-compressor-part.js
181 ms
5188203.js
66 ms
2bebbf65d33bc571090827f0c7ce68a7-compressor-part.js
491 ms
gsc-clone-purple.jpg
280 ms
satchel-logo-page-001-1.jpg
279 ms
20180921_123622-1-2400x1800.jpg
448 ms
analytics.js
89 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
87 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
136 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
135 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
135 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
132 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYA.ttf
156 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYA.ttf
156 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYA.ttf
155 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDZbtY.ttf
162 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDZbtY.ttf
159 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDZbtY.ttf
159 ms
u-4n0qyriQwlOrhSvowK_l521wRZVsf_.ttf
164 ms
u-440qyriQwlOrhSvowK_l5-ciZJ.ttf
165 ms
u-4n0qyriQwlOrhSvowK_l52xwNZVsf_.ttf
194 ms
u-4n0qyriQwlOrhSvowK_l52_wFZVsf_.ttf
163 ms
fontawesome-webfont.woff
259 ms
collect
45 ms
collect
121 ms
satchelpdx.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
satchelpdx.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
satchelpdx.com SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Satchelpdx.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 Satchelpdx.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.
satchelpdx.com
Open Graph data is detected on the main page of Satchel Pdx. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: