Tools & Wizards About Us
infor.digital screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

infor.digital

Infor | ERP simplified and preconfigured for your industry

Page Load Speed

4.2 sec in total

First Response

290 ms

Resources Loaded

2.8 sec

Page Rendered

1.1 sec

infor.digital screenshot

About Website

Welcome to infor.digital homepage info - get ready to check Infor best content right away, or after learning these important things about infor.digital

Infor is the best ERP solution. It is a simplified ERP preconfigured to be industry-specific for fast implementation on a platform with world-class cloud security.

Visit infor.digital

Key Findings

We analyzed Infor.digital page load time and found that the first response time was 290 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

infor.digital performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

24/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value6,320 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.362

30/100

15%

TTI (Time to Interactive)

Value25.7 s

0/100

10%

Network Requests Diagram

www.infor.com

290 ms

gtm.js

206 ms

e8b5d70b9baf8789.css

27 ms

586965b73cf50444.css

43 ms

polyfills-c67a75d1b6f99dc8.js

37 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Infor.digital, 29% (14 requests) were made to Infor.com and 10% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (335 ms) relates to the external source Dam.infor.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 440.4 kB (19%)

Content Size

2.3 MB

After Optimization

1.9 MB

  • HTML
  • Images

In fact, the total size of Infor.digital main page is 2.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. 80% 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. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 253.0 kB

  • Original 315.3 kB
  • After minification 315.2 kB
  • After compression 62.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. 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 253.0 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 187.4 kB

  • Original 2.0 MB
  • After minification 1.8 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. Infor images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 11 (26%)

Requests Now

42

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.infor.com

www.infor.com

290 ms

gtm.js

gtm.js

206 ms

e8b5d70b9baf8789.css

e8b5d70b9baf8789.css

27 ms

586965b73cf50444.css

586965b73cf50444.css

43 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

37 ms

webpack-d5fa33962f971de7.js

webpack-d5fa33962f971de7.js

117 ms

framework-149d197030a4a702.js

framework-149d197030a4a702.js

120 ms

main-2771a713559eb520.js

main-2771a713559eb520.js

118 ms

_app-844628b62e8399de.js

_app-844628b62e8399de.js

159 ms

75fc9c18-40134325ca6388e2.js

75fc9c18-40134325ca6388e2.js

118 ms

91-36f89da4e0c78881.js

91-36f89da4e0c78881.js

161 ms

29-e4b752b0277a1541.js

29-e4b752b0277a1541.js

164 ms

%5B%5B...path%5D%5D-b78e15eb5bc69eca.js

%5B%5B...path%5D%5D-b78e15eb5bc69eca.js

163 ms

_buildManifest.js

_buildManifest.js

162 ms

_ssgManifest.js

_ssgManifest.js

163 ms

ad827b8c9f524d28aa7f8dec8911da96

ad827b8c9f524d28aa7f8dec8911da96

292 ms

ec0960d62843430ca58fda66ed689f47

ec0960d62843430ca58fda66ed689f47

131 ms

ad827b8c9f524d28aa7f8dec8911da96

ad827b8c9f524d28aa7f8dec8911da96

234 ms

fad0f98258f6496fb68c93521ef7fd23

fad0f98258f6496fb68c93521ef7fd23

173 ms

ad827b8c9f524d28aa7f8dec8911da96

ad827b8c9f524d28aa7f8dec8911da96

300 ms

33d4a95ad37949ad9935924eb5dcdc89

33d4a95ad37949ad9935924eb5dcdc89

145 ms

a1181c4768394e898fb8f13b41d80dbf

a1181c4768394e898fb8f13b41d80dbf

174 ms

ed82af91fcd14446b6e8b7352f3778ee

ed82af91fcd14446b6e8b7352f3778ee

174 ms

57c959461922487ca233f5c83b5955ea

57c959461922487ca233f5c83b5955ea

174 ms

ed9191315ee44054b66dd365345631e2

ed9191315ee44054b66dd365345631e2

193 ms

abb61ac42e674f99ba7faca8abbf9baa

abb61ac42e674f99ba7faca8abbf9baa

194 ms

e57adaa4fa4b4c23916670898fd21274

e57adaa4fa4b4c23916670898fd21274

196 ms

30542ecb1ddb477081474fab0de49503

30542ecb1ddb477081474fab0de49503

225 ms

9a152b43256c4c3296955dff8189eeee

9a152b43256c4c3296955dff8189eeee

225 ms

e9c3abc695a7492b9f847c5dc1ddb98c

e9c3abc695a7492b9f847c5dc1ddb98c

223 ms

2b3132faae46459b95192d4310841198

2b3132faae46459b95192d4310841198

227 ms

6c7fea91c2be440bbfa63c13dee5a8fc

6c7fea91c2be440bbfa63c13dee5a8fc

235 ms

2ff967cf55e54ecaa7f4eaaa89ffa461

2ff967cf55e54ecaa7f4eaaa89ffa461

234 ms

d60b2568391445d98ec07145c551404d

d60b2568391445d98ec07145c551404d

247 ms

a9848c2935ed4351a44843d4c6abcaf8

a9848c2935ed4351a44843d4c6abcaf8

335 ms

e7b2d0f6f4594851825cb9d9df053409

e7b2d0f6f4594851825cb9d9df053409

258 ms

e72b89aea95d45fc925b142eddf94a7e

e72b89aea95d45fc925b142eddf94a7e

266 ms

afc7954446034da98a092b5e85c56384

afc7954446034da98a092b5e85c56384

276 ms

68e2faa255bf4725a9227a61c19db453

68e2faa255bf4725a9227a61c19db453

268 ms

40a8ef37f1a94c719d4e3c4d72c291e4

40a8ef37f1a94c719d4e3c4d72c291e4

290 ms

0e1cf9ad5f894654af8cec5c7ac8f100

0e1cf9ad5f894654af8cec5c7ac8f100

292 ms

4a9e96ee0f534b4b8530fc6a2292b8b7

4a9e96ee0f534b4b8530fc6a2292b8b7

291 ms

9bf7e82131164b3ca1d7a00d0453faa2

9bf7e82131164b3ca1d7a00d0453faa2

299 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPA.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPA.woff

104 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rAkw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rAkw.woff

120 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

7 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

20 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

20 ms

Accessibility Review

infor.digital accessibility score

87

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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.

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

Best Practices

infor.digital best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

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

infor.digital SEO score

91

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

infor.digital

Open Graph data is detected on the main page of Infor. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: