Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

occam.global

Homepage | Occam

Page Load Speed

2.2 sec in total

First Response

47 ms

Resources Loaded

1.2 sec

Page Rendered

1 sec

occam.global screenshot

About Website

Welcome to occam.global homepage info - get ready to check Occam best content for Australia right away, or after learning these important things about occam.global

Discover the power of IVR Automation with Razor. Streamline customer interactions, enhance efficiency, and elevate customer satisfaction.

Visit occam.global

Key Findings

We analyzed Occam.global page load time and found that the first response time was 47 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

occam.global performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

24/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value3.8 s

90/100

10%

Network Requests Diagram

occam.global

47 ms

occam.global

66 ms

www.occam.cx

230 ms

ba8bc0dc8f8af434712a502908269c5b.css

76 ms

cookie-law-info-public.js

52 ms

Our browser made a total of 160 requests to load all elements on the main page. We found that 43% of them (69 requests) were addressed to the original Occam.global, 56% (90 requests) were made to Occam.cx and 1% (1 request) were made to Secure.team8save.com. The less responsive or slowest element that took the longest time to load (338 ms) relates to the external source Occam.cx.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.7 kB (10%)

Content Size

1.3 MB

After Optimization

1.2 MB

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

HTML Optimization

-73%

Potential reduce by 136.5 kB

  • Original 187.3 kB
  • After minification 187.1 kB
  • After compression 50.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 136.5 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-0%

Potential reduce by 207 B

  • Original 220.7 kB
  • After minification 220.7 kB
  • After compression 220.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 149.7 kB
  • After minification 149.7 kB
  • After compression 149.7 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. Occam.global has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (38%)

Requests Now

80

After Optimization

50

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

Accessibility Review

occam.global accessibility score

74

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

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

occam.global best practices score

83

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

occam.global SEO score

82

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

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 Occam.global 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 Occam.global 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 Occam. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: