Tools & Wizards About Us
piepho.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

piepho.com

Piepho Moving & Storage | Minneapolis & St. Paul Movers

Page Load Speed

3.9 sec in total

First Response

361 ms

Resources Loaded

2.4 sec

Page Rendered

1.1 sec

piepho.com screenshot

About Website

Welcome to piepho.com homepage info - get ready to check Piepho best content right away, or after learning these important things about piepho.com

We offer reliable moving and storage services in the Twin Cities. We've assisted 40,000+ homeowners and businesses in MN and WI.

Visit piepho.com

Key Findings

We analyzed Piepho.com page load time and found that the first response time was 361 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

piepho.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.091

92/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

piepho.com

361 ms

www.piepho.com

296 ms

gtm.js

77 ms

css2

58 ms

style.min.css

234 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 70% of them (60 requests) were addressed to the original Piepho.com, 21% (18 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Piepho.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.1 kB (12%)

Content Size

1.0 MB

After Optimization

903.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Piepho.com main page is 1.0 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. 70% of websites need less resources to load. Images take 636.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 124.7 kB

  • Original 153.4 kB
  • After minification 148.9 kB
  • After compression 28.7 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 124.7 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 178 B

  • Original 636.5 kB
  • After minification 636.3 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. Piepho images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 177 B

  • Original 238.7 kB
  • After minification 238.7 kB
  • After compression 238.5 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 47 (76%)

Requests Now

62

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

piepho.com

piepho.com

361 ms

www.piepho.com

www.piepho.com

296 ms

gtm.js

gtm.js

77 ms

css2

css2

58 ms

style.min.css

style.min.css

234 ms

style.css

style.css

203 ms

button.css

button.css

42 ms

simpay-public.min.css

simpay-public.min.css

189 ms

simpay-public-pro.min.css

simpay-public-pro.min.css

213 ms

js_composer.min.css

js_composer.min.css

301 ms

formreset.min.css

formreset.min.css

255 ms

datepicker.min.css

datepicker.min.css

256 ms

formsmain.min.css

formsmain.min.css

413 ms

readyclass.min.css

readyclass.min.css

392 ms

browsers.min.css

browsers.min.css

401 ms

style.css

style.css

522 ms

jquery.min.js

jquery.min.js

377 ms

jquery-migrate.min.js

jquery-migrate.min.js

510 ms

jquery.json.min.js

jquery.json.min.js

615 ms

gravityforms.min.js

gravityforms.min.js

620 ms

conditional_logic.min.js

conditional_logic.min.js

483 ms

utils.min.js

utils.min.js

650 ms

js

js

98 ms

captaincore-analytics.js

captaincore-analytics.js

679 ms

platform.js

platform.js

39 ms

script.min.js

script.min.js

606 ms

35 ms

accounting.min.js

accounting.min.js

751 ms

dom-ready.min.js

dom-ready.min.js

607 ms

hooks.min.js

hooks.min.js

827 ms

i18n.min.js

i18n.min.js

827 ms

a11y.min.js

a11y.min.js

827 ms

url.min.js

url.min.js

828 ms

api-fetch.min.js

api-fetch.min.js

828 ms

simpay-public-pro-upe.min.js

simpay-public-pro-upe.min.js

950 ms

lazysizes.min.js

lazysizes.min.js

857 ms

core.min.js

core.min.js

960 ms

datepicker.min.js

datepicker.min.js

1013 ms

datepicker-legacy.min.js

datepicker-legacy.min.js

981 ms

datepicker.min.js

datepicker.min.js

918 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

982 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

1028 ms

vendor-theme.min.js

vendor-theme.min.js

1032 ms

platform.js

platform.js

45 ms

scripts-theme.min.js

scripts-theme.min.js

960 ms

map_data.js

map_data.js

876 ms

intl-tel-input-utility.js

intl-tel-input-utility.js

948 ms

script.js

script.js

1035 ms

js_composer_front.min.js

js_composer_front.min.js

983 ms

akismet-frontend.js

akismet-frontend.js

963 ms

home-section_1-bg.jpg

home-section_1-bg.jpg

813 ms

home-section_3-bg_1.png

home-section_3-bg_1.png

654 ms

home-section_3-bg_2.png

home-section_3-bg_2.png

653 ms

home-section_3-bg_3.png

home-section_3-bg_3.png

818 ms

home-section_3-bg_4.png

home-section_3-bg_4.png

832 ms

home-section_4-bg.jpg

home-section_4-bg.jpg

775 ms

pxiByp8kv8JHgFVrLCz7V1g.woff

pxiByp8kv8JHgFVrLCz7V1g.woff

59 ms

pxiByp8kv8JHgFVrLDD4V1g.woff

pxiByp8kv8JHgFVrLDD4V1g.woff

127 ms

pxiByp8kv8JHgFVrLBT5V1g.woff

pxiByp8kv8JHgFVrLBT5V1g.woff

145 ms

pxiByp8kv8JHgFVrLEj6V1g.woff

pxiByp8kv8JHgFVrLEj6V1g.woff

147 ms

pxiByp8kv8JHgFVrLGT9V1g.woff

pxiByp8kv8JHgFVrLGT9V1g.woff

146 ms

pxiEyp8kv8JHgFVrFJM.woff

pxiEyp8kv8JHgFVrFJM.woff

147 ms

pxiByp8kv8JHgFVrLDz8V1g.woff

pxiByp8kv8JHgFVrLDz8V1g.woff

146 ms

pxiByp8kv8JHgFVrLFj_V1g.woff

pxiByp8kv8JHgFVrLFj_V1g.woff

146 ms

pxiGyp8kv8JHgFVrLPTedA.woff

pxiGyp8kv8JHgFVrLPTedA.woff

147 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

147 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

148 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff

148 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

149 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

147 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

149 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

150 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff

218 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff

216 ms

fa-solid-900.ttf

fa-solid-900.ttf

837 ms

fa-regular-400.ttf

fa-regular-400.ttf

865 ms

js

js

116 ms

home-section_6-bg.jpg

home-section_6-bg.jpg

1072 ms

footer_form-bg.jpg

footer_form-bg.jpg

861 ms

arrow.png

arrow.png

940 ms

fa-brands-400.ttf

fa-brands-400.ttf

1031 ms

logo.svg

logo.svg

559 ms

logo-alt.svg

logo-alt.svg

726 ms

page-heading-image.png

page-heading-image.png

632 ms

home-section_2-img_1.png

home-section_2-img_1.png

753 ms

picturefill.min.js

picturefill.min.js

495 ms

Accessibility Review

piepho.com accessibility score

81

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

[aria-*] attributes do not match their roles

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

piepho.com SEO score

74

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

piepho.com

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