Tools & Wizards About Us
principal.cl screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

principal.cl

Homepage | Principal

Page Load Speed

2.2 sec in total

First Response

138 ms

Resources Loaded

1.6 sec

Page Rendered

389 ms

principal.cl screenshot

About Website

Click here to check amazing Principal content for Chile. Otherwise, check out these important facts you probably never knew about principal.cl

Visit principal.cl

Key Findings

We analyzed Principal.cl page load time and found that the first response time was 138 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

principal.cl performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value25.0 s

0/100

10%

TBT (Total Blocking Time)

Value8,260 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value41.4 s

0/100

10%

Network Requests Diagram

www.principal.cl

138 ms

gtm.js

152 ms

core.min.css

82 ms

css_LMf7pD0EkMMcn3GAMYbwP6wuVKRzm8nRQeNddrkHg0Y.css

71 ms

grid.min.css

78 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 39% of them (28 requests) were addressed to the original Principal.cl, 40% (29 requests) were made to Principalcdn.com and 6% (4 requests) were made to Principal-chatbot-dev.azurewebsites.net. The less responsive or slowest element that took the longest time to load (370 ms) relates to the external source Principal-chatbot-dev.azurewebsites.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (45%)

Content Size

3.7 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Principal.cl main page is 3.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 85.1 kB

  • Original 100.5 kB
  • After minification 83.7 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 16.8 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 85.1 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 56.3 kB

  • Original 1.5 MB
  • After minification 1.4 MB

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. Principal images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 156.1 kB

  • Original 512.9 kB
  • After minification 511.9 kB
  • After compression 356.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 156.1 kB or 30% of the original size.

CSS Optimization

-87%

Potential reduce by 1.4 MB

  • Original 1.6 MB
  • After minification 1.2 MB
  • After compression 200.6 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. Principal.cl needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 87% of the original size.

Requests Breakdown

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

Requests Now

63

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.principal.cl

www.principal.cl

138 ms

gtm.js

gtm.js

152 ms

core.min.css

core.min.css

82 ms

css_LMf7pD0EkMMcn3GAMYbwP6wuVKRzm8nRQeNddrkHg0Y.css

css_LMf7pD0EkMMcn3GAMYbwP6wuVKRzm8nRQeNddrkHg0Y.css

71 ms

grid.min.css

grid.min.css

78 ms

css_Of1k-MKUKMptHWe5eFS7kTMStn9jay-7rOdIdHFceFY.css

css_Of1k-MKUKMptHWe5eFS7kTMStn9jay-7rOdIdHFceFY.css

142 ms

button.min.css

button.min.css

76 ms

css_ms_nr_X5YOyEPUwqqz5RuVnw9h-rkdUj3VR49jirOWk.css

css_ms_nr_X5YOyEPUwqqz5RuVnw9h-rkdUj3VR49jirOWk.css

120 ms

index.login.css

index.login.css

104 ms

css_v52pnKvzGMwJsCsbQob1gLXKl-3n3S7iFQHISwvruAA.css

css_v52pnKvzGMwJsCsbQob1gLXKl-3n3S7iFQHISwvruAA.css

136 ms

font-awesome.min.css

font-awesome.min.css

103 ms

css_nnx4V1oymteGlm8S4ruUYgRQoJkUePZYoh20oDxr81M.css

css_nnx4V1oymteGlm8S4ruUYgRQoJkUePZYoh20oDxr81M.css

150 ms

css_y4A6nBm2Xz1ouuQkU8Zt3dUC3wVG9DDiKRhNOpGCD94.css

css_y4A6nBm2Xz1ouuQkU8Zt3dUC3wVG9DDiKRhNOpGCD94.css

128 ms

core.min.css

core.min.css

92 ms

grid.min.css

grid.min.css

88 ms

button.min.css

button.min.css

92 ms

botchat.css

botchat.css

370 ms

bot.css

bot.css

363 ms

superFooter.min.css

superFooter.min.css

103 ms

hero.min.css

hero.min.css

128 ms

fullWidthImg.min.css

fullWidthImg.min.css

118 ms

welcomeBanner.min.css

welcomeBanner.min.css

116 ms

card.min.css

card.min.css

125 ms

cardGrid.min.css

cardGrid.min.css

123 ms

articlePreview.min.css

articlePreview.min.css

134 ms

modal.min.css

modal.min.css

136 ms

tag.min.css

tag.min.css

136 ms

tout.min.css

tout.min.css

137 ms

navigationPrimary.min.css

navigationPrimary.min.css

139 ms

css_qoj0c8Vb6qA395iEhbnSujeq4FvRHSww703446VFEYo.css

css_qoj0c8Vb6qA395iEhbnSujeq4FvRHSww703446VFEYo.css

194 ms

js_Uxv8-54-3jywDk9RDagcnWap_n-t9RzodDNaZzii-e4.js

js_Uxv8-54-3jywDk9RDagcnWap_n-t9RzodDNaZzii-e4.js

182 ms

page.js

page.js

121 ms

js_ub51wMJa7a5s4rqOWoE6LS41MCo9CtIgrOXRfmOjgqI.js

js_ub51wMJa7a5s4rqOWoE6LS41MCo9CtIgrOXRfmOjgqI.js

147 ms

core.min.js

core.min.js

137 ms

core.min.js

core.min.js

133 ms

js_riRjSq1AQfmey-wgxputY1J1WDU7mMu5o7iRF_vA_SI.js

js_riRjSq1AQfmey-wgxputY1J1WDU7mMu5o7iRF_vA_SI.js

148 ms

gtm.js

gtm.js

148 ms

gtag.js

gtag.js

153 ms

js_phXKPmSMhGp37D0n-DZc5R_EtF5BJevbvBrEf3XoACs.js

js_phXKPmSMhGp37D0n-DZc5R_EtF5BJevbvBrEf3XoACs.js

153 ms

index.bundle.js

index.bundle.js

107 ms

botchat.js

botchat.js

356 ms

main-prod.js

main-prod.js

345 ms

hero.min.js

hero.min.js

138 ms

fullWidthImg.min.js

fullWidthImg.min.js

137 ms

js_3o8Jd6kZFTeG7wVY_OPzgfcm_sWYg--5DNHUrKQWwfk.js

js_3o8Jd6kZFTeG7wVY_OPzgfcm_sWYg--5DNHUrKQWwfk.js

153 ms

card.min.js

card.min.js

137 ms

js_cVU0t62MvlhWBj2N-KijK4eHn7sa4JbU1dpY0mdu68o.js

js_cVU0t62MvlhWBj2N-KijK4eHn7sa4JbU1dpY0mdu68o.js

152 ms

cardGrid.min.js

cardGrid.min.js

144 ms

articlePreview.min.js

articlePreview.min.js

144 ms

modal.min.js

modal.min.js

144 ms

js_tFzjQtV37xAUlxzw0y5wjV4cgEodCoAw72l21KvpZs0.js

js_tFzjQtV37xAUlxzw0y5wjV4cgEodCoAw72l21KvpZs0.js

153 ms

public-integration.js

public-integration.js

116 ms

js_blYaskN-oPjCqgs7x5QyyiFsY81w3HsDmKMgWCiXJOM.js

js_blYaskN-oPjCqgs7x5QyyiFsY81w3HsDmKMgWCiXJOM.js

151 ms

navigationDrupal.min.js

navigationDrupal.min.js

143 ms

js_dLUC6eG47Yx-1tUjy0O12Ebc1wJhuY8ogPiJPRYw09I.js

js_dLUC6eG47Yx-1tUjy0O12Ebc1wJhuY8ogPiJPRYw09I.js

152 ms

logo.svg

logo.svg

153 ms

CC%202%20%282%29.jpeg

CC%202%20%282%29.jpeg

217 ms

BANNER-SALMO%CC%81N-mobile.jpg

BANNER-SALMO%CC%81N-mobile.jpg

219 ms

imgcsa.jpeg

imgcsa.jpeg

169 ms

AdobeStock_499114369%20%283%29.jpeg

AdobeStock_499114369%20%283%29.jpeg

213 ms

AdobeStock_513255347%20%281%29.jpeg

AdobeStock_513255347%20%281%29.jpeg

194 ms

ads.png

ads.png

220 ms

dark

dark

158 ms

icon-search.svg

icon-search.svg

105 ms

GettyImages-1209265565_PFG%201.png

GettyImages-1209265565_PFG%201.png

167 ms

jsapi-v1.js

jsapi-v1.js

122 ms

cobrowse-jsapi-v1.js

cobrowse-jsapi-v1.js

180 ms

FSElliotWeb-Bold.woff

FSElliotWeb-Bold.woff

78 ms

FSElliotWeb-Regular.woff

FSElliotWeb-Regular.woff

78 ms

FSElliotPro-Light.woff

FSElliotPro-Light.woff

78 ms

sm.25.html

sm.25.html

74 ms

eso.BRQnzO8v.js

eso.BRQnzO8v.js

133 ms

Accessibility Review

principal.cl accessibility score

89

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

principal.cl best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

principal.cl SEO score

98

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

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

principal.cl

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