Tools & Wizards About Us
cache4mag.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cache4mag.com

Magento Cache Extension | Full Page Cache | Cache4Mag

Page Load Speed

6.6 sec in total

First Response

1.9 sec

Resources Loaded

4.5 sec

Page Rendered

240 ms

cache4mag.com screenshot

About Website

Visit cache4mag.com now to see the best up-to-date Cache4 Mag content and also check out these interesting facts you probably never knew about cache4mag.com

Magento full page cache solution for Magento shop for better performance - better search engine ranking, better shopping experience, better conversion rates.

Visit cache4mag.com

Key Findings

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

Performance Metrics

cache4mag.com performance score

0

Network Requests Diagram

www.cache4mag.com

1852 ms

css

16 ms

font-awesome.css

101 ms

jquery.bxslider.css

196 ms

photoswipe.css

198 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 88% of them (58 requests) were addressed to the original Cache4mag.com, 8% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Cache4mag.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 969.4 kB (63%)

Content Size

1.5 MB

After Optimization

565.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cache4mag.com main page is 1.5 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. 60% of websites need less resources to load. Javascripts take 799.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 17.6 kB

  • Original 24.0 kB
  • After minification 24.0 kB
  • After compression 6.3 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 17.6 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 6.9 kB

  • Original 345.9 kB
  • After minification 338.9 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. Cache4 Mag images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 632.6 kB

  • Original 799.2 kB
  • After minification 561.4 kB
  • After compression 166.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 632.6 kB or 79% of the original size.

CSS Optimization

-85%

Potential reduce by 312.2 kB

  • Original 366.2 kB
  • After minification 294.3 kB
  • After compression 54.0 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. Cache4mag.com needs all CSS files to be minified and compressed as it can save up to 312.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (81%)

Requests Now

59

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.cache4mag.com

www.cache4mag.com

1852 ms

css

css

16 ms

font-awesome.css

font-awesome.css

101 ms

jquery.bxslider.css

jquery.bxslider.css

196 ms

photoswipe.css

photoswipe.css

198 ms

bootstrap.css

bootstrap.css

304 ms

extra_style.css

extra_style.css

198 ms

styles.css

styles.css

314 ms

responsive.css

responsive.css

199 ms

superfish.css

superfish.css

293 ms

camera.css

camera.css

298 ms

widgets.css

widgets.css

295 ms

cloud-zoom.css

cloud-zoom.css

300 ms

catalogsale.css

catalogsale.css

392 ms

jquery-1.7.min.js

jquery-1.7.min.js

593 ms

superfish.js

superfish.js

502 ms

scripts.js

scripts.js

503 ms

prototype.js

prototype.js

613 ms

ccard.js

ccard.js

504 ms

validation.js

validation.js

505 ms

builder.js

builder.js

505 ms

effects.js

effects.js

507 ms

dragdrop.js

dragdrop.js

509 ms

controls.js

controls.js

590 ms

slider.js

slider.js

589 ms

js.js

js.js

610 ms

form.js

form.js

611 ms

translate.js

translate.js

687 ms

cookies.js

cookies.js

687 ms

cloud-zoom.1.0.2.min.js

cloud-zoom.1.0.2.min.js

688 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

693 ms

jquery.mobile.customized.min.js

jquery.mobile.customized.min.js

703 ms

bootstrap.js

bootstrap.js

741 ms

jquery.carouFredSel-6.2.1.js

jquery.carouFredSel-6.2.1.js

889 ms

jquery.touchSwipe.js

jquery.touchSwipe.js

791 ms

jquery.bxslider.js

jquery.bxslider.js

792 ms

carousel.js

carousel.js

792 ms

logo.png

logo.png

800 ms

Cache4Mag-Verpackung-V4.png

Cache4Mag-Verpackung-V4.png

1005 ms

seo.png

seo.png

800 ms

ranking.png

ranking.png

895 ms

conversion.png

conversion.png

799 ms

experience.png

experience.png

804 ms

chart.png

chart.png

703 ms

sanum.png

sanum.png

1087 ms

icon_cart.png

icon_cart.png

676 ms

sm_shadow1.jpg

sm_shadow1.jpg

676 ms

icon_sm1.png

icon_sm1.png

685 ms

sm_shadow2.jpg

sm_shadow2.jpg

771 ms

icon_sm2.png

icon_sm2.png

686 ms

sm_shadow3.jpg

sm_shadow3.jpg

687 ms

icon_sm3.png

icon_sm3.png

695 ms

sm_shadow4.jpg

sm_shadow4.jpg

694 ms

icon_sm4.png

icon_sm4.png

779 ms

icon-revenue.png

icon-revenue.png

780 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

974 ms

RjgO7rYTmqiVp7vzi-Q5UT8E0i7KZn-EPnyo3HZu7kw.woff

RjgO7rYTmqiVp7vzi-Q5UT8E0i7KZn-EPnyo3HZu7kw.woff

4 ms

DXI1ORHCpsQm3Vp6mXoaTYraN7vELC11_xip9Rz-hMs.woff

DXI1ORHCpsQm3Vp6mXoaTYraN7vELC11_xip9Rz-hMs.woff

10 ms

MTP_ySUJH_bn48VBG8sNSoraN7vELC11_xip9Rz-hMs.woff

MTP_ySUJH_bn48VBG8sNSoraN7vELC11_xip9Rz-hMs.woff

11 ms

k3k702ZOKiLJc3WVjuplzIraN7vELC11_xip9Rz-hMs.woff

k3k702ZOKiLJc3WVjuplzIraN7vELC11_xip9Rz-hMs.woff

11 ms

EInbV5DfGHOiMmvb1Xr-horaN7vELC11_xip9Rz-hMs.woff

EInbV5DfGHOiMmvb1Xr-horaN7vELC11_xip9Rz-hMs.woff

11 ms

big_arr.png

big_arr.png

787 ms

sm_arr.png

sm_arr.png

707 ms

ga.js

ga.js

15 ms

__utm.gif

__utm.gif

11 ms

print.css

print.css

99 ms

SEO Factors

cache4mag.com SEO score

0

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

cache4mag.com

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