Tools & Wizards About Us
xgoogle.co.za screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

xgoogle.co.za

News in South Africa

Page Load Speed

7.4 sec in total

First Response

760 ms

Resources Loaded

6.3 sec

Page Rendered

396 ms

xgoogle.co.za screenshot

About Website

Welcome to xgoogle.co.za homepage info - get ready to check Xgoogle best content for South Africa right away, or after learning these important things about xgoogle.co.za

Latest Updates from News, Accidents, Robberies and Incidents

Visit xgoogle.co.za

Key Findings

We analyzed Xgoogle.co.za page load time and found that the first response time was 760 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

xgoogle.co.za performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value17.1 s

0/100

10%

TBT (Total Blocking Time)

Value25,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value38.1 s

0/100

10%

Network Requests Diagram

xgoogle.co.za

760 ms

css

358 ms

font-awesome.min.css

354 ms

37adb30d2f.js

383 ms

material-kit.css

1095 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 15% of them (12 requests) were addressed to the original Xgoogle.co.za, 13% (10 requests) were made to Fonts.gstatic.com and 11% (9 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Nari.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 114.8 kB (18%)

Content Size

637.1 kB

After Optimization

522.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xgoogle.co.za main page is 637.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 300.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 76.7 kB

  • Original 95.2 kB
  • After minification 82.4 kB
  • After compression 18.5 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 12.8 kB, which is 13% 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 76.7 kB or 81% of the original size.

Image Optimization

-7%

Potential reduce by 20.9 kB

  • Original 300.8 kB
  • After minification 279.9 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. Xgoogle images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 13.3 kB

  • Original 185.9 kB
  • After minification 185.9 kB
  • After compression 172.6 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

-7%

Potential reduce by 4.0 kB

  • Original 55.2 kB
  • After minification 55.2 kB
  • After compression 51.3 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. Xgoogle.co.za has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 47 (68%)

Requests Now

69

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xgoogle.co.za

xgoogle.co.za

760 ms

css

css

358 ms

font-awesome.min.css

font-awesome.min.css

354 ms

37adb30d2f.js

37adb30d2f.js

383 ms

material-kit.css

material-kit.css

1095 ms

demo.css

demo.css

602 ms

core-set-overwrite.css

core-set-overwrite.css

598 ms

adsbygoogle.js

adsbygoogle.js

304 ms

jquery.min.js

jquery.min.js

1045 ms

popper.min.js

popper.min.js

562 ms

bootstrap-material-design.min.js

bootstrap-material-design.min.js

808 ms

moment.min.js

moment.min.js

1442 ms

bootstrap-datetimepicker.js

bootstrap-datetimepicker.js

1043 ms

nouislider.min.js

nouislider.min.js

1044 ms

material-kit.js

material-kit.js

1441 ms

zrt_lookup.html

zrt_lookup.html

29 ms

show_ads_impl.js

show_ads_impl.js

310 ms

nari_icon.jpg

nari_icon.jpg

2709 ms

new.png

new.png

594 ms

bull1111553914606.jpg

bull1111553914606.jpg

2709 ms

google_play2.png

google_play2.png

1856 ms

sdk.js

sdk.js

245 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

128 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

349 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

351 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

355 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OWaA.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OWaA.ttf

356 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf

355 ms

sdk.js

sdk.js

167 ms

cookie.js

cookie.js

223 ms

integrator.js

integrator.js

201 ms

ads

ads

856 ms

analytics.js

analytics.js

76 ms

ads

ads

630 ms

collect

collect

46 ms

collect

collect

64 ms

reactive_library.js

reactive_library.js

107 ms

integrator.js

integrator.js

125 ms

ads

ads

682 ms

zrt_lookup.html

zrt_lookup.html

110 ms

gm.png

gm.png

301 ms

5865619286570400271

5865619286570400271

92 ms

abg_lite.js

abg_lite.js

145 ms

window_focus.js

window_focus.js

182 ms

qs_click_protection.js

qs_click_protection.js

201 ms

rx_lidar.js

rx_lidar.js

279 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

201 ms

css2

css2

153 ms

shopping

shopping

255 ms

load_preloaded_resource.js

load_preloaded_resource.js

226 ms

042791247ab671b2831aa311d6583330.js

042791247ab671b2831aa311d6583330.js

464 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

208 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

514 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

516 ms

icon.png

icon.png

121 ms

shopping

shopping

455 ms

s

s

71 ms

activeview

activeview

143 ms

css

css

71 ms

YrdBSjzfIHcYhYLmavhSyO_EhBrLUWpx5ykdL7H9Kqg.js

YrdBSjzfIHcYhYLmavhSyO_EhBrLUWpx5ykdL7H9Kqg.js

12 ms

ea8FacM9Wef3EJPWRrHjgE4B6CnlZxHVDv79pA.ttf

ea8FacM9Wef3EJPWRrHjgE4B6CnlZxHVDv79pA.ttf

12 ms

ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBg3etBD7SQ.ttf

ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBg3etBD7SQ.ttf

12 ms

85254efcadaacab5fed344cbf203b7e7.js

85254efcadaacab5fed344cbf203b7e7.js

8 ms

c471d9b7113df21a6cf58632ab968748.js

c471d9b7113df21a6cf58632ab968748.js

354 ms

cookie_push_onload.html

cookie_push_onload.html

338 ms

css

css

59 ms

dpixel

dpixel

723 ms

sodar

sodar

668 ms

activeview

activeview

657 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

582 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

582 ms

sodar2.js

sodar2.js

107 ms

pixel

pixel

278 ms

runner.html

runner.html

61 ms

aframe

aframe

235 ms

pixel

pixel

247 ms

pixel

pixel

231 ms

pixel

pixel

58 ms

pixel

pixel

28 ms

pixel

pixel

39 ms

Accessibility Review

xgoogle.co.za accessibility score

58

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

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

High

Image elements do not have [alt] attributes

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

xgoogle.co.za 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

xgoogle.co.za SEO score

83

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 Xgoogle.co.za 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 Xgoogle.co.za 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

xgoogle.co.za

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