Tools & Wizards About Us
wallies.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wallies.com

Your Sewing Pattern Destination

Page Load Speed

1.9 sec in total

First Response

359 ms

Resources Loaded

1.4 sec

Page Rendered

178 ms

wallies.com screenshot

About Website

Visit wallies.com now to see the best up-to-date Wallies content for United States and also check out these interesting facts you probably never knew about wallies.com

Wall decals, wall stickers, wall murals, and wall graphics in different themes from Wallies. Plus peel and stick chalkboard in all different shapes and sizes.

Visit wallies.com

Key Findings

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

Performance Metrics

wallies.com performance score

0

Network Requests Diagram

wallies.com

359 ms

jquery-1.10.2.min.js

278 ms

mighty_menu.js

119 ms

cart_ajax.js

239 ms

swfobject.js

125 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 93% of them (54 requests) were addressed to the original Wallies.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (482 ms) belongs to the original domain Wallies.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 510.8 kB (56%)

Content Size

909.3 kB

After Optimization

398.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wallies.com main page is 909.3 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. Javascripts take 514.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 26.0 kB

  • Original 33.0 kB
  • After minification 31.3 kB
  • After compression 7.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 26.0 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 2.6 kB

  • Original 240.9 kB
  • After minification 238.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. Wallies images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 378.2 kB

  • Original 514.7 kB
  • After minification 458.9 kB
  • After compression 136.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 378.2 kB or 73% of the original size.

CSS Optimization

-86%

Potential reduce by 103.9 kB

  • Original 120.6 kB
  • After minification 68.7 kB
  • After compression 16.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. Wallies.com needs all CSS files to be minified and compressed as it can save up to 103.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (66%)

Requests Now

56

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wallies.com

wallies.com

359 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

278 ms

mighty_menu.js

mighty_menu.js

119 ms

cart_ajax.js

cart_ajax.js

239 ms

swfobject.js

swfobject.js

125 ms

flying_cart.js

flying_cart.js

119 ms

jkl-parsexml.js

jkl-parsexml.js

180 ms

account_ajax.js

account_ajax.js

235 ms

post_form.js

post_form.js

178 ms

jquery-ui-1.10.3.custom.min.js

jquery-ui-1.10.3.custom.min.js

482 ms

jquery-cookie.js

jquery-cookie.js

239 ms

jquery.jcarousel.pack.js

jquery.jcarousel.pack.js

239 ms

jquery-ui.css

jquery-ui.css

3 ms

mighty_menu.css

mighty_menu.css

301 ms

default.css

default.css

301 ms

checkout.css

checkout.css

356 ms

color.css

color.css

301 ms

layout.css

layout.css

335 ms

jquery.jcarousel.css

jquery.jcarousel.css

353 ms

jcarousel.css

jcarousel.css

354 ms

page_cookies.php

page_cookies.php

313 ms

topBack.jpg

topBack.jpg

81 ms

logo.png

logo.png

120 ms

cart_btn.gif

cart_btn.gif

73 ms

checkout_btn.gif

checkout_btn.gif

75 ms

logo_small.png

logo_small.png

73 ms

search_btn.gif

search_btn.gif

72 ms

emailBack.gif

emailBack.gif

110 ms

sign_up_btn.gif

sign_up_btn.gif

119 ms

first_tab.gif

first_tab.gif

120 ms

last_tab.gif

last_tab.gif

121 ms

whats_new.gif

whats_new.gif

122 ms

menu_top.gif

menu_top.gif

168 ms

menu_arrow_right.gif

menu_arrow_right.gif

178 ms

menu_bottom.gif

menu_bottom.gif

175 ms

catalog.jpg

catalog.jpg

234 ms

Wallieshome-chalkboard.jpg

Wallieshome-chalkboard.jpg

354 ms

FB_small_logo2.jpg

FB_small_logo2.jpg

174 ms

brands_arrow.gif

brands_arrow.gif

219 ms

home_baby.jpg

home_baby.jpg

284 ms

home_chalkborder.jpg

home_chalkborder.jpg

289 ms

big_wall_stickers.jpg

big_wall_stickers.jpg

233 ms

201303BottomDryErase.jpg

201303BottomDryErase.jpg

278 ms

201303BottomBigMurals.jpg

201303BottomBigMurals.jpg

403 ms

home_wallcandy_arts.jpg

home_wallcandy_arts.jpg

293 ms

home_elephants_wall.jpg

home_elephants_wall.jpg

394 ms

home_butchharold.jpg

home_butchharold.jpg

399 ms

home_FB.jpg

home_FB.jpg

348 ms

walliespinterest.jpg

walliespinterest.jpg

353 ms

footerBack.jpg

footerBack.jpg

404 ms

login_btn.gif

login_btn.gif

406 ms

password_btn.gif

password_btn.gif

414 ms

create_account.gif

create_account.gif

453 ms

continue_btn.gif

continue_btn.gif

459 ms

ga.js

ga.js

31 ms

__utm.gif

__utm.gif

12 ms

collect

collect

55 ms

menu_arrow_down.gif

menu_arrow_down.gif

60 ms

SEO Factors

wallies.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wallies.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 Wallies.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

wallies.com

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