952 ms in total
219 ms
640 ms
93 ms
Visit portlandgreens.org now to see the best up-to-date Portlandgreens content and also check out these interesting facts you probably never knew about portlandgreens.org
Katanya sih kalau udah nyoba Bunda128 susah berpaling. Daripada cuma dengar kata orang, mending buktikan sendiri keseruannya hari ini!
Visit portlandgreens.orgWe analyzed Portlandgreens.org page load time and found that the first response time was 219 ms and then it took 733 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.
portlandgreens.org performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value5.5 s
18/100
25%
Value8.0 s
22/100
10%
Value1,800 ms
10/100
30%
Value0.055
98/100
15%
Value13.6 s
11/100
10%
219 ms
60 ms
67 ms
68 ms
71 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that all of those requests were addressed to Portlandgreens.org and no external sources were called. The less responsive or slowest element that took the longest time to load (283 ms) belongs to the original domain Portlandgreens.org.
Page size can be reduced by 116.6 kB (76%)
154.1 kB
37.5 kB
In fact, the total size of Portlandgreens.org main page is 154.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. 15% of websites need less resources to load. CSS take 79.9 kB which makes up the majority of the site volume.
Potential reduce by 20.1 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 20.1 kB or 80% of the original size.
Potential reduce by 2 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. Portlandgreens images are well optimized though.
Potential reduce by 29.7 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 29.7 kB or 61% of the original size.
Potential reduce by 66.7 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. Portlandgreens.org needs all CSS files to be minified and compressed as it can save up to 66.7 kB or 83% of the original size.
Number of requests can be reduced by 40 (82%)
49
9
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Portlandgreens. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
portlandgreens.org
219 ms
node.css
60 ms
defaults.css
67 ms
system.css
68 ms
system-menus.css
71 ms
user.css
70 ms
content-module.css
71 ms
ctools.css
88 ms
filefield.css
96 ms
nice_menus.css
97 ms
nice_menus_default.css
98 ms
panels.css
100 ms
uc_order.css
98 ms
uc_product.css
118 ms
uc_store.css
125 ms
fieldgroup.css
127 ms
views.css
127 ms
twocol_bricks.css
128 ms
html-reset.css
129 ms
wireframes.css
148 ms
layout-liquid.css
155 ms
page-backgrounds.css
157 ms
tabs.css
157 ms
messages.css
157 ms
pages.css
160 ms
block-editing.css
177 ms
blocks.css
185 ms
navigation.css
186 ms
views-styles.css
187 ms
nodes.css
187 ms
comments.css
191 ms
forms.css
207 ms
fields.css
214 ms
mystyles.css
216 ms
mymenu.css
218 ms
jquery.js
283 ms
drupal.js
216 ms
superfish.js
198 ms
jquery.bgiframe.min.js
199 ms
nice_menus.js
197 ms
panels.js
196 ms
script.js
201 ms
pacificgreens_logo.gif
35 ms
pdxpgp.gif
44 ms
donate-button.gif
36 ms
seperator.gif
37 ms
arrow-down.png
37 ms
gp-logo.gif
43 ms
sub_sep.gif
66 ms
print.css
35 ms
portlandgreens.org 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
portlandgreens.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
portlandgreens.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Portlandgreens.org 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 Portlandgreens.org 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.
portlandgreens.org
Open Graph description is not detected on the main page of Portlandgreens. 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: