Tools & Wizards About Us
allia2.com.co screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

allia2.com.co

SISTEMA INDISPONIBLE / SISTEMA INDISPONIVEL /SYSTEM UNAVAILABLE

Page Load Speed

5 sec in total

First Response

255 ms

Resources Loaded

4.6 sec

Page Rendered

146 ms

allia2.com.co screenshot

About Website

Click here to check amazing Allia 2 content. Otherwise, check out these important facts you probably never knew about allia2.com.co

Allianz

Visit allia2.com.co

Key Findings

We analyzed Allia2.com.co page load time and found that the first response time was 255 ms 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

allia2.com.co performance score

0

Network Requests Diagram

allia2.com.co

255 ms

www.allianz.co

1808 ms

aui.css

233 ms

main.css

310 ms

main.css

309 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Allia2.com.co, 78% (52 requests) were made to Allianz.co and 6% (4 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Allianz.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (76%)

Content Size

3.3 MB

After Optimization

788.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Allia2.com.co main page is 3.3 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. 40% of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 31.9 kB

  • Original 39.4 kB
  • After minification 39.0 kB
  • After compression 7.4 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 31.9 kB or 81% of the original size.

Image Optimization

-28%

Potential reduce by 156.7 kB

  • Original 562.0 kB
  • After minification 405.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. Obviously, Allia 2 needs image optimization as it can save up to 156.7 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-86%

Potential reduce by 1.9 MB

  • Original 2.2 MB
  • After minification 1.1 MB
  • After compression 307.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 1.9 MB or 86% of the original size.

CSS Optimization

-87%

Potential reduce by 438.9 kB

  • Original 507.2 kB
  • After minification 408.2 kB
  • After compression 68.3 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. Allia2.com.co needs all CSS files to be minified and compressed as it can save up to 438.9 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

52

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Allia 2. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

allia2.com.co

allia2.com.co

255 ms

www.allianz.co

www.allianz.co

1808 ms

aui.css

aui.css

233 ms

main.css

main.css

310 ms

main.css

main.css

309 ms

main.css

main.css

322 ms

main.css

main.css

323 ms

main.css

main.css

339 ms

everything.jsp

everything.jsp

341 ms

main.js

main.js

407 ms

main.js

main.js

408 ms

main.css

main.css

542 ms

general.js

general.js

431 ms

jquery.sudoSlider.min.js

jquery.sudoSlider.min.js

454 ms

main.js

main.js

451 ms

main.css

main.css

206 ms

main.css

main.css

313 ms

main.css

main.css

224 ms

main.css

main.css

246 ms

main.css

main.css

234 ms

everything.jsp

everything.jsp

1190 ms

main.js

main.js

249 ms

main.js

main.js

249 ms

bg.png

bg.png

123 ms

header_1px.png

header_1px.png

112 ms

company_logo

company_logo

131 ms

399d9ef1-a60c-467a-b807-dc5c81fb29dd

399d9ef1-a60c-467a-b807-dc5c81fb29dd

133 ms

f2735ac7-ad17-4b2d-a6eb-2f3af9be4fb9

f2735ac7-ad17-4b2d-a6eb-2f3af9be4fb9

103 ms

e4e36bdf-8715-4bcb-b65f-fa6b2530840d

e4e36bdf-8715-4bcb-b65f-fa6b2530840d

424 ms

trennlinie_654.gif

trennlinie_654.gif

208 ms

7c06c446-0aeb-4535-ab99-416332767a18

7c06c446-0aeb-4535-ab99-416332767a18

657 ms

d7cc391f-c051-42e1-ba2e-22a67806fa77

d7cc391f-c051-42e1-ba2e-22a67806fa77

365 ms

5cd165d0-d7d5-4306-a911-4133e1ce3a68

5cd165d0-d7d5-4306-a911-4133e1ce3a68

374 ms

35a78bb2-51a6-4684-b555-17ad0d7ece45

35a78bb2-51a6-4684-b555-17ad0d7ece45

324 ms

8a0ed675-a268-4310-b4e3-aae60b0cddb7

8a0ed675-a268-4310-b4e3-aae60b0cddb7

480 ms

top_arrow.gif

top_arrow.gif

430 ms

d90722bc-51ff-4c08-aacd-2f9d6b6b8076

d90722bc-51ff-4c08-aacd-2f9d6b6b8076

472 ms

959ba7e5-9b29-4e91-bea4-477b276aae06

959ba7e5-9b29-4e91-bea4-477b276aae06

499 ms

80f17c81-04f9-4cd0-a85e-5fe36611d2c9

80f17c81-04f9-4cd0-a85e-5fe36611d2c9

536 ms

7a04d792-4e2f-4d1d-bce7-8a814ef7281b

7a04d792-4e2f-4d1d-bce7-8a814ef7281b

541 ms

8ebf20ce-5a49-4e83-ba6b-c50f0eee3d95

8ebf20ce-5a49-4e83-ba6b-c50f0eee3d95

590 ms

f1af1561-943a-4798-80ee-d8431f95d79f

f1af1561-943a-4798-80ee-d8431f95d79f

601 ms

b5dd1054-afeb-4635-bd95-7d49b2115bd8

b5dd1054-afeb-4635-bd95-7d49b2115bd8

632 ms

c0c447b7-ed80-4978-8967-a6323ede9e42

c0c447b7-ed80-4978-8967-a6323ede9e42

650 ms

dac5114a-ceca-44cd-a72c-342ebdee8952

dac5114a-ceca-44cd-a72c-342ebdee8952

655 ms

analytics.js

analytics.js

44 ms

667 ms

arrow_prev.png

arrow_prev.png

664 ms

arrow_next.png

arrow_next.png

691 ms

dots.png

dots.png

705 ms

LightningBolt.js

LightningBolt.js

64 ms

collect

collect

20 ms

collect

collect

59 ms

f2735ac7-ad17-4b2d-a6eb-2f3af9be4fb9

f2735ac7-ad17-4b2d-a6eb-2f3af9be4fb9

675 ms

utag.js

utag.js

284 ms

x71.html

x71.html

22 ms

jquery.min.js

jquery.min.js

64 ms

ga-audiences

ga-audiences

38 ms

89a8c69b-52ad-414b-aa8a-433ab1f12445

89a8c69b-52ad-414b-aa8a-433ab1f12445

543 ms

imp

imp

13 ms

utag.js

utag.js

9 ms

mobile.html

mobile.html

228 ms

d90722bc-51ff-4c08-aacd-2f9d6b6b8076

d90722bc-51ff-4c08-aacd-2f9d6b6b8076

344 ms

event

event

9 ms

utag.9.js

utag.9.js

9 ms

128 ms

bounce

bounce

23 ms

SEO Factors

allia2.com.co SEO score

0

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Allia2.com.co can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Allia2.com.co 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

allia2.com.co

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