Tools & Wizards About Us

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

eloqua.com

Marketing Cloud | Oracle

Page Load Speed

2.1 sec in total

First Response

134 ms

Resources Loaded

1.4 sec

Page Rendered

516 ms

About Website

Welcome to eloqua.com homepage info - get ready to check Eloqua best content for United States right away, or after learning these important things about eloqua.com

Oracle CX Marketing is an integrated set of digital marketing solutions that help B2B and B2C marketers deliver personalized experiences.

Visit eloqua.com

Key Findings

We analyzed Eloqua.com page load time and found that the first response time was 134 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

eloqua.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

43/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value12,330 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.83

4/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

marketing-to-businesses.html

134 ms

jquery.js

39 ms

truste-oraclelib.js

414 ms

omc.css

54 ms

updown.min.js

15 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Eloqua.com, 6% (4 requests) were made to Oracleimg.com and 6% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (414 ms) relates to the external source Oracle.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 445.8 kB (25%)

Content Size

1.8 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Eloqua.com main page is 1.8 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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 101.8 kB

  • Original 117.1 kB
  • After minification 72.3 kB
  • After compression 15.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 44.8 kB, which is 38% 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 101.8 kB or 87% of the original size.

Image Optimization

-10%

Potential reduce by 137.3 kB

  • Original 1.4 MB
  • After minification 1.3 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. Eloqua images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 206.6 kB

  • Original 291.6 kB
  • After minification 257.3 kB
  • After compression 85.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 206.6 kB or 71% of the original size.

Requests Breakdown

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

Requests Now

60

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

eloqua.com accessibility score

60

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

High

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

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

eloqua.com best practices score

83

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

SEO Factors

eloqua.com SEO score

98

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eloqua.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Eloqua.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

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