Tools & Wizards About Us
excelanz.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

excelanz.net

Page Load Speed

12.4 sec in total

First Response

1.6 sec

Resources Loaded

10.5 sec

Page Rendered

256 ms

excelanz.net screenshot

About Website

Welcome to excelanz.net homepage info - get ready to check Excelanz best content right away, or after learning these important things about excelanz.net

home

Visit excelanz.net

Key Findings

We analyzed Excelanz.net page load time and found that the first response time was 1.6 sec and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

excelanz.net performance score

0

Network Requests Diagram

www.excelanz.net

1566 ms

styles.css

295 ms

settings.css

757 ms

captions.css

521 ms

bootstrap.min.css

2523 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 93% of them (52 requests) were addressed to the original Excelanz.net, 5% (3 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Excelanz.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 456.0 kB (55%)

Content Size

834.7 kB

After Optimization

378.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Excelanz.net main page is 834.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. Javascripts take 381.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 25.3 kB

  • Original 31.3 kB
  • After minification 26.1 kB
  • After compression 6.0 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 5.2 kB, which is 17% 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 25.3 kB or 81% of the original size.

Image Optimization

-7%

Potential reduce by 18.8 kB

  • Original 263.7 kB
  • After minification 244.8 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. Excelanz images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 279.4 kB

  • Original 381.2 kB
  • After minification 349.0 kB
  • After compression 101.8 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 279.4 kB or 73% of the original size.

CSS Optimization

-84%

Potential reduce by 132.6 kB

  • Original 158.5 kB
  • After minification 148.7 kB
  • After compression 25.9 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. Excelanz.net needs all CSS files to be minified and compressed as it can save up to 132.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (52%)

Requests Now

52

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.excelanz.net

www.excelanz.net

1566 ms

styles.css

styles.css

295 ms

settings.css

settings.css

757 ms

captions.css

captions.css

521 ms

bootstrap.min.css

bootstrap.min.css

2523 ms

bootstrap-responsive.min.css

bootstrap-responsive.min.css

842 ms

style.css

style.css

558 ms

screen.php

screen.php

2082 ms

prettyPhoto.css

prettyPhoto.css

1097 ms

jquery.js

jquery.js

2717 ms

jquery-migrate.min.js

jquery-migrate.min.js

1003 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

1280 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

2263 ms

mctagmap.css

mctagmap.css

1361 ms

css

css

24 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

1462 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

2409 ms

jquery.form.min.js

jquery.form.min.js

1867 ms

scripts.js

scripts.js

2224 ms

jquery.modernizr.min.js

jquery.modernizr.min.js

2323 ms

jquery.isotope.min.js

jquery.isotope.min.js

3090 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

2486 ms

jquery.fitvid.js

jquery.fitvid.js

2546 ms

jquery.backstretch.min.js

jquery.backstretch.min.js

2579 ms

bootstrap.min.js

bootstrap.min.js

3136 ms

ddsmoothmenu.php

ddsmoothmenu.php

3117 ms

jquery.TwitterReader.js

jquery.TwitterReader.js

2790 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

3278 ms

screen.js

screen.js

2829 ms

mctagmap.js

mctagmap.js

3080 ms

experience-our-excellence.jpg

experience-our-excellence.jpg

591 ms

excelanz-logo1.jpg

excelanz-logo1.jpg

859 ms

search.png

search.png

898 ms

admin-ajax.php

admin-ajax.php

3523 ms

admin-ajax.php

admin-ajax.php

2301 ms

admin-ajax.php

admin-ajax.php

4106 ms

2.png

2.png

1469 ms

4.png

4.png

1929 ms

1.png

1.png

2010 ms

3.png

3.png

2380 ms

7.png

7.png

2512 ms

facebook.png

facebook.png

2282 ms

twitter.png

twitter.png

2567 ms

googleplus.png

googleplus.png

2575 ms

bgtile.jpg

bgtile.jpg

2637 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

5 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

10 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

24 ms

timer.png

timer.png

1931 ms

loader.gif

loader.gif

2034 ms

shadow2.png

shadow2.png

1997 ms

menuplus.png

menuplus.png

2062 ms

arrow_left.png

arrow_left.png

282 ms

arrow_right.png

arrow_right.png

284 ms

arrow_large_left.png

arrow_large_left.png

281 ms

arrow_large_right.png

arrow_large_right.png

317 ms

SEO Factors

excelanz.net SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Excelanz.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Excelanz.net 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

excelanz.net

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