Tools & Wizards About Us
forinsia.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

forinsia.com

IIS Windows Server

Page Load Speed

4.2 sec in total

First Response

329 ms

Resources Loaded

3.6 sec

Page Rendered

234 ms

forinsia.com screenshot

About Website

Click here to check amazing Forinsia content for Portugal. Otherwise, check out these important facts you probably never knew about forinsia.com

O Forinsia é um software de gestão da formação online para centros de formação ou formação interna de empresas Inscrições - Pagamentos online - Alertas - Questionários - Emissão de documentos - Rela...

Visit forinsia.com

Key Findings

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

Performance Metrics

forinsia.com performance score

0

Network Requests Diagram

forinsia.com

329 ms

FORINSIA

651 ms

public-cachekey6536.css

216 ms

dropdown-menu-cachekey3568.css

216 ms

resourceplone.app.discussion.stylesheetsdiscussion-cachekey3256.css

219 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Forinsia.com, 87% (46 requests) were made to Insia.pt and 8% (4 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Insia.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 620.4 kB (46%)

Content Size

1.3 MB

After Optimization

719.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Forinsia.com main page is 1.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 711.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 117.9 kB

  • Original 153.3 kB
  • After minification 148.5 kB
  • After compression 35.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 117.9 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 22.0 kB

  • Original 474.4 kB
  • After minification 452.4 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. Forinsia images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 480.5 kB

  • Original 711.9 kB
  • After minification 710.7 kB
  • After compression 231.4 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 480.5 kB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (47%)

Requests Now

51

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forinsia.com

forinsia.com

329 ms

FORINSIA

FORINSIA

651 ms

public-cachekey6536.css

public-cachekey6536.css

216 ms

dropdown-menu-cachekey3568.css

dropdown-menu-cachekey3568.css

216 ms

resourceplone.app.discussion.stylesheetsdiscussion-cachekey3256.css

resourceplone.app.discussion.stylesheetsdiscussion-cachekey3256.css

219 ms

bootstrap.min-cachekey7848.css

bootstrap.min-cachekey7848.css

643 ms

resourceplonetheme.insia.stylesheetsmain-cachekey2838.css

resourceplonetheme.insia.stylesheetsmain-cachekey2838.css

327 ms

resourcejquery-ui-themessunburstjqueryui-cachekey2520.css

resourcejquery-ui-themessunburstjqueryui-cachekey2520.css

424 ms

resourcecollective.js.fullcalendarfullcalendar-cachekey8292.css

resourcecollective.js.fullcalendarfullcalendar-cachekey8292.css

323 ms

solgema_contextualcontentmenu-cachekey7902.css

solgema_contextualcontentmenu-cachekey7902.css

323 ms

responsive-cachekey6312.css

responsive-cachekey6312.css

329 ms

at-cachekey1201.kss

at-cachekey1201.kss

428 ms

resourceplone.app.jquery-cachekey2832.js

resourceplone.app.jquery-cachekey2832.js

744 ms

resourcecollective.infinitecarousel.jsjquery-1.7.1-cachekey7592.js

resourcecollective.infinitecarousel.jsjquery-1.7.1-cachekey7592.js

648 ms

jquery-integration-cachekey0259.js

jquery-integration-cachekey0259.js

765 ms

resourcedropdown-menu-cachekey2833.js

resourcedropdown-menu-cachekey2833.js

530 ms

bootstrap-integration-cachekey8927.js

bootstrap-integration-cachekey8927.js

637 ms

resourcecollective.infinitecarousel.jsjquery.infinitecarousel3.min-cachekey4372.js

resourcecollective.infinitecarousel.jsjquery.infinitecarousel3.min-cachekey4372.js

638 ms

resourcecollective.infinitecarousel.jseasing-cachekey7450.js

resourcecollective.infinitecarousel.jseasing-cachekey7450.js

761 ms

resourcejquery-ui.min-cachekey7424.js

resourcejquery-ui.min-cachekey7424.js

1281 ms

resourcecollective.js.fullcalendarfullcalendar.min-cachekey7923.js

resourcecollective.js.fullcalendarfullcalendar.min-cachekey7923.js

762 ms

resourcecollective.js.colorpicker.jseye-cachekey0352.js

resourcecollective.js.colorpicker.jseye-cachekey0352.js

761 ms

main.js

main.js

854 ms

addthis_widget.js

addthis_widget.js

10 ms

gb.gif

gb.gif

140 ms

pt.gif

pt.gif

139 ms

insia_logo.png

insia_logo.png

140 ms

copy_of_cd_carrossel.jpg

copy_of_cd_carrossel.jpg

770 ms

tile

tile

203 ms

tile

tile

193 ms

tile

tile

290 ms

tile

tile

306 ms

tile

tile

309 ms

tile

tile

342 ms

thumb

thumb

345 ms

thumb

thumb

420 ms

thumb

thumb

427 ms

thumb

thumb

488 ms

thumb

thumb

459 ms

forinsia_enterpriseV3.png

forinsia_enterpriseV3.png

560 ms

forinsia_suiteV3.png

forinsia_suiteV3.png

631 ms

forinsia_startV3.png

forinsia_startV3.png

535 ms

tile

tile

602 ms

tile

tile

618 ms

tile

tile

649 ms

tile

tile

684 ms

tile

tile

717 ms

spinner.gif

spinner.gif

736 ms

analytics.js

analytics.js

44 ms

300lo.json

300lo.json

58 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

50 ms

layers.e5ea973510bf60b3db41.js

layers.e5ea973510bf60b3db41.js

21 ms

pt.js

pt.js

36 ms

SEO Factors

forinsia.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forinsia.com 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 Portuguese. Our system also found out that Forinsia.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

forinsia.com

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