Tools & Wizards About Us
pdxrestore.org screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

pdxrestore.org

Home | Portland Region ReStores

Page Load Speed

6.3 sec in total

First Response

213 ms

Resources Loaded

4.4 sec

Page Rendered

1.7 sec

pdxrestore.org screenshot

About Website

Welcome to pdxrestore.org homepage info - get ready to check Pdx Re Sto best content for United States right away, or after learning these important things about pdxrestore.org

Visit pdxrestore.org

Key Findings

We analyzed Pdxrestore.org page load time and found that the first response time was 213 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

pdxrestore.org performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value65.2 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value410 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

pdxrestore.org

213 ms

pdxrestore.org

455 ms

style.min.css

81 ms

style.css

159 ms

style.css

225 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 95% of them (37 requests) were addressed to the original Pdxrestore.org, 3% (1 request) were made to Static.resupply.tech and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Pdxrestore.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 737.9 kB (3%)

Content Size

23.7 MB

After Optimization

23.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pdxrestore.org main page is 23.7 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. 40% of websites need less resources to load. Images take 23.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 43.3 kB

  • Original 55.1 kB
  • After minification 48.3 kB
  • After compression 11.8 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. This page needs HTML code to be minified as it can gain 6.8 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 43.3 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 623.0 kB

  • Original 23.4 MB
  • After minification 22.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. Pdx Re Sto images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 11.7 kB

  • Original 97.9 kB
  • After minification 97.9 kB
  • After compression 86.2 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 11.7 kB or 12% of the original size.

CSS Optimization

-47%

Potential reduce by 59.9 kB

  • Original 127.3 kB
  • After minification 109.5 kB
  • After compression 67.4 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. Pdxrestore.org needs all CSS files to be minified and compressed as it can save up to 59.9 kB or 47% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (56%)

Requests Now

34

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pdxrestore.org

pdxrestore.org

213 ms

pdxrestore.org

pdxrestore.org

455 ms

style.min.css

style.min.css

81 ms

style.css

style.css

159 ms

style.css

style.css

225 ms

style.css

style.css

225 ms

style.css

style.css

226 ms

index.css

index.css

226 ms

bulma.css

bulma.css

244 ms

style.css

style.css

310 ms

all.min.css

all.min.css

373 ms

style.css

style.css

299 ms

app.css

app.css

299 ms

sassy-social-share-public.css

sassy-social-share-public.css

300 ms

jquery.min.js

jquery.min.js

334 ms

jquery-migrate.min.js

jquery-migrate.min.js

387 ms

resupply-partner-button2.js

resupply-partner-button2.js

51 ms

accordion-blocks.min.js

accordion-blocks.min.js

407 ms

navigation.js

navigation.js

407 ms

smoothscroll.js

smoothscroll.js

504 ms

sassy-social-share-public.js

sassy-social-share-public.js

504 ms

popup.js

popup.js

503 ms

gtm.js

gtm.js

149 ms

HHR-BW-Logo-V2.png

HHR-BW-Logo-V2.png

174 ms

HFHPortlandRegionOR_Hz_Black.png

HFHPortlandRegionOR_Hz_Black.png

174 ms

ReStore-HFH-photo1.png

ReStore-HFH-photo1.png

1357 ms

ReStore-Volunteer-1-scaled.png

ReStore-Volunteer-1-scaled.png

3279 ms

construction-4by3.jpg

construction-4by3.jpg

322 ms

fabian-blank-pElSkGRA2NU-unsplash.jpg

fabian-blank-pElSkGRA2NU-unsplash.jpg

985 ms

girlshugging.jpg

girlshugging.jpg

929 ms

H4H-ReStore_Beaverton_Sept2022_IMG_4528-HDR_JasonQuigley-scaled.jpg

H4H-ReStore_Beaverton_Sept2022_IMG_4528-HDR_JasonQuigley-scaled.jpg

990 ms

H4H-ReStore_Beaverton_Sept2022_IMG_4476_JasonQuigley-scaled.jpg

H4H-ReStore_Beaverton_Sept2022_IMG_4476_JasonQuigley-scaled.jpg

624 ms

SMSM-2024-400x300.png

SMSM-2024-400x300.png

700 ms

Guest-Bedroom_after-3-2-400x300.jpg

Guest-Bedroom_after-3-2-400x300.jpg

775 ms

Info-Post-Holidays-400x300.png

Info-Post-Holidays-400x300.png

851 ms

HHR-White-Logo-V2.png

HHR-White-Logo-V2.png

925 ms

fa-solid-900.woff

fa-solid-900.woff

904 ms

fa-regular-400.woff

fa-regular-400.woff

908 ms

fa-brands-400.woff

fa-brands-400.woff

963 ms

Accessibility Review

pdxrestore.org accessibility score

79

Accessibility Issues

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

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.

Best Practices

pdxrestore.org 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

pdxrestore.org SEO score

70

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

Social Sharing Optimization

pdxrestore.org

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