Tools & Wizards About Us
junkeco.com screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    86% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

junkeco.com

Junk Eco - Twin Cities Junk Removal Service. We haul furniture, appliances, trash, metal, clothes, and much more from Minneapolis, St. Paul and suburb...

Page Load Speed

1.1 sec in total

First Response

161 ms

Resources Loaded

861 ms

Page Rendered

124 ms

junkeco.com screenshot

About Website

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

Junk Eco provides junk recycling, removal, and disposal to Minnesota, Twin Cities, Edina, and surrounding suburbs.

Visit junkeco.com

Key Findings

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

Performance Metrics

junkeco.com performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

95/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

24/100

25%

SI (Speed Index)

Value1.6 s

100/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

junkeco.com

161 ms

junkeco.com

265 ms

ga.js

20 ms

logo_header_junk_eco_284w_x_100h.jpg

124 ms

junk_eco_bottom_facebook_twitter_linker.jpg

243 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 85% of them (23 requests) were addressed to the original Junkeco.com, 7% (2 requests) were made to Ssl.google-analytics.com and 4% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (366 ms) belongs to the original domain Junkeco.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.8 kB (4%)

Content Size

598.7 kB

After Optimization

574.9 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-69%

Potential reduce by 10.7 kB

  • Original 15.5 kB
  • After minification 15.0 kB
  • After compression 4.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. 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 10.7 kB or 69% of the original size.

Image Optimization

-2%

Potential reduce by 13.1 kB

  • Original 566.1 kB
  • After minification 553.0 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. Junk Eco images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

We found no issues to fix!

Requests Now

23

After Optimization

23

  • Images
  • JavaScript

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Junk Eco. According to our analytics all requests are already optimized.

Network Requests Diagram

junkeco.com

junkeco.com

161 ms

junkeco.com

junkeco.com

265 ms

ga.js

ga.js

20 ms

logo_header_junk_eco_284w_x_100h.jpg

logo_header_junk_eco_284w_x_100h.jpg

124 ms

junk_eco_bottom_facebook_twitter_linker.jpg

junk_eco_bottom_facebook_twitter_linker.jpg

243 ms

logo_header_spacer_brandstatement_mid.gif

logo_header_spacer_brandstatement_mid.gif

186 ms

logo_header_right_cooltruck_284x100.jpg

logo_header_right_cooltruck_284x100.jpg

187 ms

homepage_sideright_panel_addon_aug4_2010.gif

homepage_sideright_panel_addon_aug4_2010.gif

243 ms

button_services_up.jpg

button_services_up.jpg

244 ms

button_whatwetake_up.jpg

button_whatwetake_up.jpg

249 ms

button_pricing_up.jpg

button_pricing_up.jpg

303 ms

button_availability_up.jpg

button_availability_up.jpg

246 ms

button_contact_up.jpg

button_contact_up.jpg

303 ms

recycling_junk_image_copyright_junkeco.jpg

recycling_junk_image_copyright_junkeco.jpg

361 ms

call_junkeco_graphic.jpg

call_junkeco_graphic.jpg

363 ms

book_junkeco_angieslistv3.jpg

book_junkeco_angieslistv3.jpg

308 ms

mn_bg_support_local_business.jpg

mn_bg_support_local_business.jpg

310 ms

whats_your_junk_say_book_onlinev4.jpg

whats_your_junk_say_book_onlinev4.jpg

366 ms

junkeco_bottom_linkbar_homepage.jpg

junkeco_bottom_linkbar_homepage.jpg

366 ms

__utm.gif

__utm.gif

28 ms

collect

collect

46 ms

ga-audiences

ga-audiences

47 ms

button_services_over.jpg

button_services_over.jpg

63 ms

button_whatwetake_over.jpg

button_whatwetake_over.jpg

63 ms

button_pricing_over.jpg

button_pricing_over.jpg

63 ms

button_availability_over.jpg

button_availability_over.jpg

65 ms

button_contact_over.jpg

button_contact_over.jpg

64 ms

Accessibility Review

junkeco.com accessibility score

54

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Links do not have a discernible name

Best Practices

junkeco.com best practices score

75

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

Serves images with low resolution

SEO Factors

junkeco.com SEO score

58

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Junkeco.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Junkeco.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

junkeco.com

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