Tools & Wizards About Us
vitrue.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

vitrue.com

UNIVERSAL-FRAGMENTS

Page Load Speed

2.6 sec in total

First Response

592 ms

Resources Loaded

1.9 sec

Page Rendered

67 ms

vitrue.com screenshot

About Website

Visit vitrue.com now to see the best up-to-date Vitrue content for Kenya and also check out these interesting facts you probably never knew about vitrue.com

The fragment library for all generic fragments used across sites

Visit vitrue.com

Key Findings

We analyzed Vitrue.com page load time and found that the first response time was 592 ms and then it took 2 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

vitrue.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

index.html

592 ms

ocom-mosaic.css

79 ms

master-mosaic.css

43 ms

jquery.js

47 ms

oraclelib-mosaic.js

77 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Vitrue.com, 10% (4 requests) were made to Oracleimg.com and 8% (3 requests) were made to Dpm.demdex.net. The less responsive or slowest element that took the longest time to load (810 ms) relates to the external source Oracle.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 372.7 kB (54%)

Content Size

687.7 kB

After Optimization

315.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Vitrue.com main page is 687.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 659.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 20.7 kB

  • Original 28.1 kB
  • After minification 23.7 kB
  • After compression 7.4 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 4.4 kB, which is 16% 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 20.7 kB or 74% of the original size.

Image Optimization

-31%

Potential reduce by 119 B

  • Original 384 B
  • After minification 265 B

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, Vitrue needs image optimization as it can save up to 119 B or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 351.9 kB

  • Original 659.3 kB
  • After minification 659.3 kB
  • After compression 307.3 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 351.9 kB or 53% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (41%)

Requests Now

22

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

index.html

index.html

592 ms

ocom-mosaic.css

ocom-mosaic.css

79 ms

master-mosaic.css

master-mosaic.css

43 ms

jquery.js

jquery.js

47 ms

oraclelib-mosaic.js

oraclelib-mosaic.js

77 ms

satelliteLib-e598c5b61e39a10b402e048e87dd27b0f1cd2d4c.js

satelliteLib-e598c5b61e39a10b402e048e87dd27b0f1cd2d4c.js

32 ms

notice

notice

111 ms

ocom-mosaic-base.css

ocom-mosaic-base.css

105 ms

OracleSans-Rg.woff

OracleSans-Rg.woff

72 ms

OracleSansCd-Lt.woff

OracleSansCd-Lt.woff

165 ms

OracleSans-Lt.woff

OracleSans-Lt.woff

71 ms

OracleSans-SBd.woff

OracleSans-SBd.woff

92 ms

OracleSansCd-Bd.woff

OracleSansCd-Bd.woff

91 ms

OracleSans-XBd.woff

OracleSans-XBd.woff

107 ms

ora_ocom.js

ora_ocom.js

113 ms

DXNLE-YBWWY-AR74T-WMD99-77VRA

DXNLE-YBWWY-AR74T-WMD99-77VRA

124 ms

f02v7-bg.png

f02v7-bg.png

248 ms

email.gif

email.gif

610 ms

print_icon.gif

print_icon.gif

810 ms

oraclesans-lt.woff

oraclesans-lt.woff

80 ms

oraclesans-rg.woff

oraclesans-rg.woff

53 ms

oraclesans-ult.woff

oraclesans-ult.woff

183 ms

oraclesanscd-rg.woff

oraclesanscd-rg.woff

189 ms

oraclesans-bd.woff

oraclesans-bd.woff

182 ms

066625.gif

066625.gif

196 ms

oraclesanscd-bd.woff

oraclesanscd-bd.woff

217 ms

oraclesans-sbd.woff

oraclesans-sbd.woff

181 ms

oraclesans-xbd.woff

oraclesans-xbd.woff

184 ms

ora_code_ocom.js

ora_code_ocom.js

45 ms

ora_code.js

ora_code.js

42 ms

config.json

config.json

153 ms

oraclesanscd-lt.woff

oraclesanscd-lt.woff

128 ms

id

id

92 ms

UNIVERSAL-MENUCONTENTindex.html

UNIVERSAL-MENUCONTENTindex.html

373 ms

handlebars-ocom.js

handlebars-ocom.js

86 ms

dest5.html

dest5.html

50 ms

id

id

50 ms

ibs:dpid=411&dpuuid=Zjh2aAAAAJPvNwN_

ibs:dpid=411&dpuuid=Zjh2aAAAAJPvNwN_

9 ms

id

id

6 ms

Accessibility Review

vitrue.com accessibility score

82

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

[role]s do not have all required [aria-*] attributes

High

[aria-*] attributes do not have valid values

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.

Best Practices

vitrue.com best practices score

50

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

vitrue.com SEO score

62

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

High

Page is blocked from indexing

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

vitrue.com

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