Report Summary

  • 0

    Performance

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

inforges.es

Inforges. Transformación digital y SAP Business One Pymes

Page Load Speed

5.2 sec in total

First Response

365 ms

Resources Loaded

4.6 sec

Page Rendered

241 ms

inforges.es screenshot

About Website

Click here to check amazing Inforges content for Spain. Otherwise, check out these important facts you probably never knew about inforges.es

Inforges, expertos en transformación digital e implantación de software de gestión ERP SAP para Pymes en España. 45 años de experiencia

Visit inforges.es

Key Findings

We analyzed Inforges.es page load time and found that the first response time was 365 ms and then it took 4.9 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

inforges.es performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.4 s

0/100

25%

SI (Speed Index)

Value20.8 s

0/100

10%

TBT (Total Blocking Time)

Value7,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.032

2/100

15%

TTI (Time to Interactive)

Value28.8 s

0/100

10%

Network Requests Diagram

inforges.es

365 ms

www.inforges.es

2531 ms

editstyle.css

222 ms

flexslider.css

226 ms

style.css

686 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 66% of them (44 requests) were addressed to the original Inforges.es, 9% (6 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Inforges.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 813.3 kB (56%)

Content Size

1.5 MB

After Optimization

646.7 kB

In fact, the total size of Inforges.es 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. 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. Javascripts take 685.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 43.3 kB

  • Original 53.6 kB
  • After minification 46.9 kB
  • After compression 10.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. This page needs HTML code to be minified as it can gain 6.6 kB, which is 12% 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 43.3 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 15.6 kB

  • Original 368.3 kB
  • After minification 352.7 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. Inforges images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 463.1 kB

  • Original 685.4 kB
  • After minification 668.6 kB
  • After compression 222.3 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 463.1 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 291.3 kB

  • Original 352.7 kB
  • After minification 351.4 kB
  • After compression 61.4 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. Inforges.es needs all CSS files to be minified and compressed as it can save up to 291.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (43%)

Requests Now

58

After Optimization

33

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

Accessibility Review

inforges.es accessibility score

71

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

inforges.es best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

inforges.es SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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 Inforges.es 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 Inforges.es 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

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