Tools & Wizards About Us
portaldemo.interworks.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

portaldemo.interworks.com

Curator CMS Introduction | Curator by InterWorks

Page Load Speed

3.9 sec in total

First Response

75 ms

Resources Loaded

3.5 sec

Page Rendered

363 ms

portaldemo.interworks.com screenshot

About Website

Click here to check amazing Portaldemo Inter Works content for United States. Otherwise, check out these important facts you probably never knew about portaldemo.interworks.com

Curator by InterWorks : Embedded Analytics Portal

Visit portaldemo.interworks.com

Key Findings

We analyzed Portaldemo.interworks.com page load time and found that the first response time was 75 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 65% of websites can load faster.

Performance Metrics

portaldemo.interworks.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value21.2 s

0/100

10%

TBT (Total Blocking Time)

Value13,030 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value33.2 s

0/100

10%

Network Requests Diagram

portaldemo.interworks.com

75 ms

demos

2003 ms

bfaad8fd940d1958694ba253cd7adddd-1721824804

149 ms

select2.min.css

189 ms

gut7hrb.css

18 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Portaldemo.interworks.com, 61% (40 requests) were made to Curator.interworks.com and 11% (7 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Curator.interworks.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 811.9 kB (38%)

Content Size

2.1 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Portaldemo.interworks.com main page is 2.1 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. 65% of websites need less resources to load. Images take 983.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 140.4 kB

  • Original 168.7 kB
  • After minification 150.7 kB
  • After compression 28.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 18.0 kB, which is 11% 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 140.4 kB or 83% of the original size.

Image Optimization

-13%

Potential reduce by 127.0 kB

  • Original 983.0 kB
  • After minification 856.1 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, Portaldemo Inter Works needs image optimization as it can save up to 127.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-39%

Potential reduce by 221.2 kB

  • Original 562.0 kB
  • After minification 562.0 kB
  • After compression 340.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 221.2 kB or 39% of the original size.

CSS Optimization

-76%

Potential reduce by 323.3 kB

  • Original 425.5 kB
  • After minification 424.8 kB
  • After compression 102.2 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. Portaldemo.interworks.com needs all CSS files to be minified and compressed as it can save up to 323.3 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (57%)

Requests Now

58

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

portaldemo.interworks.com

portaldemo.interworks.com

75 ms

demos

demos

2003 ms

bfaad8fd940d1958694ba253cd7adddd-1721824804

bfaad8fd940d1958694ba253cd7adddd-1721824804

149 ms

select2.min.css

select2.min.css

189 ms

gut7hrb.css

gut7hrb.css

18 ms

framework.extras.css

framework.extras.css

187 ms

page_frontend.css

page_frontend.css

189 ms

theme_1.css

theme_1.css

259 ms

jquery.min.js

jquery.min.js

269 ms

utils.js

utils.js

228 ms

analytics.js

analytics.js

248 ms

js.cookie.js

js.cookie.js

248 ms

log-js-errors.js

log-js-errors.js

249 ms

polyfill.min.js

polyfill.min.js

279 ms

tile.js

tile.js

309 ms

select2.min.js

select2.min.js

482 ms

tutorial.js

tutorial.js

311 ms

translation.js

translation.js

322 ms

navigation_menu.js

navigation_menu.js

321 ms

search.js

search.js

343 ms

page_frontend.js

page_frontend.js

475 ms

script.js

script.js

41 ms

blog

blog

426 ms

js

js

69 ms

js

js

134 ms

0de112232d9880eadf51fbae748532c3-1721824804

0de112232d9880eadf51fbae748532c3-1721824804

499 ms

5239373b5a9f3b73d7bceaf1ec933927-1721824804

5239373b5a9f3b73d7bceaf1ec933927-1721824804

424 ms

caa8ecd289aa7a9da688035ae8fecfd6-1715798442

caa8ecd289aa7a9da688035ae8fecfd6-1715798442

423 ms

gtm.js

gtm.js

53 ms

p.css

p.css

23 ms

matomo.js

matomo.js

904 ms

array.js

array.js

162 ms

pd.js

pd.js

141 ms

7s69T-lZUUY

7s69T-lZUUY

245 ms

kvABuayVnDY

kvABuayVnDY

341 ms

L06p85Xgie4

L06p85Xgie4

753 ms

yHk-u-oIth8

yHk-u-oIth8

884 ms

63b5d9ebd4beb812712984.svg

63b5d9ebd4beb812712984.svg

187 ms

page-break

page-break

238 ms

showcase-demo

showcase-demo

887 ms

iwsl-demo

iwsl-demo

878 ms

healthcare-demo

healthcare-demo

562 ms

edu-demo

edu-demo

875 ms

finance-demo

finance-demo

876 ms

scout-demo

scout-demo

878 ms

intergy-demo

intergy-demo

881 ms

retail-demo

retail-demo

882 ms

interburger-demo

interburger-demo

883 ms

salesforce-demo-preview.png

salesforce-demo-preview.png

884 ms

curator-logo-opaquefull

curator-logo-opaquefull

888 ms

d

d

16 ms

d

d

28 ms

d

d

28 ms

d

d

29 ms

d

d

28 ms

d

d

27 ms

analytics

analytics

753 ms

123 ms

JavaScript%20Error:%20%22SyntaxError:%20Expected%20an%20identifier%20but%20found%20'contentTopManuallySet'%20instead%22%20%7C%20Page:%20tutorial.js%20%7C%20Line:%20430

JavaScript%20Error:%20%22SyntaxError:%20Expected%20an%20identifier%20but%20found%20'contentTopManuallySet'%20instead%22%20%7C%20Page:%20tutorial.js%20%7C%20Line:%20430

665 ms

JavaScript%20Error:%20%22SyntaxError:%20Unexpected%20token%20'%3E'%22%20%7C%20Page:%20navigation_menu.js%20%7C%20Line:%20287

JavaScript%20Error:%20%22SyntaxError:%20Unexpected%20token%20'%3E'%22%20%7C%20Page:%20navigation_menu.js%20%7C%20Line:%20287

762 ms

JavaScript%20Error:%20%22SyntaxError:%20Invalid%20character:%20'%60'%22%20%7C%20Page:%20page_frontend.js%20%7C%20Line:%20554

JavaScript%20Error:%20%22SyntaxError:%20Invalid%20character:%20'%60'%22%20%7C%20Page:%20page_frontend.js%20%7C%20Line:%20554

761 ms

www-player.css

www-player.css

22 ms

www-embed-player.js

www-embed-player.js

45 ms

base.js

base.js

98 ms

JavaScript%20Error:%20%22TypeError:%20undefined%20is%20not%20a%20function%20(evaluating%20'$.request')%22%20%7C%20Page:%20search.js%20%7C%20Line:%2012

JavaScript%20Error:%20%22TypeError:%20undefined%20is%20not%20a%20function%20(evaluating%20'$.request')%22%20%7C%20Page:%20search.js%20%7C%20Line:%2012

748 ms

JavaScript%20Error:%20%22ReferenceError:%20Can't%20find%20variable:%20Utils%22%20%7C%20Page:%20demos%20%7C%20Line:%20206

JavaScript%20Error:%20%22ReferenceError:%20Can't%20find%20variable:%20Utils%22%20%7C%20Page:%20demos%20%7C%20Line:%20206

748 ms

Accessibility Review

portaldemo.interworks.com accessibility score

66

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-*] attributes do not match their roles

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

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

High

Image elements do not have [alt] attributes

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>).

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

portaldemo.interworks.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

portaldemo.interworks.com SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Portaldemo.interworks.com 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 Portaldemo.interworks.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

portaldemo.interworks.com

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