Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

portal.net

WebCenter Portal - Portal and Composite Applications Solution | Oracle

Page Load Speed

1.8 sec in total

First Response

107 ms

Resources Loaded

1.3 sec

Page Rendered

396 ms

About Website

Click here to check amazing Portal content for Belarus. Otherwise, check out these important facts you probably never knew about portal.net

Find out how Oracle WebCenter Portal allows organizations to easily create intranets, extranets, composite applications, and self-service portals.

Visit portal.net

Key Findings

We analyzed Portal.net page load time and found that the first response time was 107 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

portal.net performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value2,530 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.127

82/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

107 ms

jquery-min.js

61 ms

utag.sync.js

17 ms

utag.js

18 ms

DXNLE-YBWWY-AR74T-WMD99-77VRA

23 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Portal.net, 10% (2 requests) were made to Tms.oracle.com and 10% (2 requests) were made to Dpm.demdex.net. The less responsive or slowest element that took the longest time to load (428 ms) relates to the external source Oracle.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 447.4 kB (42%)

Content Size

1.1 MB

After Optimization

613.2 kB

In fact, the total size of Portal.net main page is 1.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. 35% of websites need less resources to load. Javascripts take 734.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 42.3 kB

  • Original 59.2 kB
  • After minification 55.2 kB
  • After compression 16.9 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 42.3 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 267.3 kB
  • After minification 267.3 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. Portal images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 405.1 kB

  • Original 734.1 kB
  • After minification 734.1 kB
  • After compression 329.0 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 405.1 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (42%)

Requests Now

19

After Optimization

11

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

Accessibility Review

portal.net accessibility score

96

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

Best Practices

portal.net best practices score

92

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

Page has valid source maps

SEO Factors

portal.net SEO score

93

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

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 Portal.net 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 Portal.net 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 Portal. 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: