southafricajournal.com

southafricajournal.com is SSL secured

Free website and domain report on southafricajournal.com

Last Updated: 17th May, 2021 Update Now
Overview

Snoop Summary for southafricajournal.com

This is a free and comprehensive report about southafricajournal.com. The domain southafricajournal.com is currently hosted on a server located in Queen Creek, Arizona in United States with the IP address 198.54.116.97, where the local currency is USD and English is the local language. If southafricajournal.com was to be sold it would possibly be worth $258 USD (based on the daily revenue potential of the website over a 24 month period). Southafricajournal.com is somewhat popular with an estimated 119 daily unique visitors. This report was last updated 17th May, 2021.

About southafricajournal.com

Site Preview: southafricajournal.com southafricajournal.com
Title: South Africa Journal - Hub for all the Latest News & Updates
Description: Hub for all the Latest News & Updates
Keywords and Tags: blogs, wiki
Related Terms: all updates
Fav Icon:
Age: Over 9 years old
Domain Created: 16th February, 2015
Domain Updated: 24th January, 2019
Domain Expires: 16th February, 2022
Review

Snoop Score

1/5

Valuation

$258 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 7,871,162
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 119
Monthly Visitors: 3,622
Yearly Visitors: 43,435
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $10 USD
Yearly Revenue: $124 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: southafricajournal.com 22
Domain Name: southafricajournal 18
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 83
Performance 88
Accessibility 96
Best Practices 93
SEO 92
Progressive Web App 45
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
88

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for southafricajournal.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 0.9 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.018
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.8 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive southafricajournal.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://southafricajournal.com/
http/1.1
0
190.74099999852
262
0
301
text/html
https://southafricajournal.com/
h2
191.24300009571
3752.6460001245
16459
98379
200
text/html
Document
https://southafricajournal.com/wp-includes/css/dist/block-library/style.min.css?ver=5.7.2
h2
3766.3940000348
4133.7510000449
9082
58171
200
text/css
Stylesheet
https://southafricajournal.com/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=5.4.1
h2
3766.5520000737
4043.1900001131
1327
2640
200
text/css
Stylesheet
https://southafricajournal.com/wp-content/themes/eggnews/assets/lib/font-awesome/css/font-awesome.min.css?ver=4.7.0
h2
3766.7900000233
4052.7670001611
7450
31000
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Poppins&ver=5.7.2
h2
3767.0270001981
3778.8520001341
1152
1020
200
text/css
Stylesheet
https://southafricajournal.com/wp-content/themes/eggnews/assets/css/eggnews.css?ver=1.0.3
h2
3767.1980001032
4139.6690001711
13871
76924
200
text/css
Stylesheet
https://southafricajournal.com/wp-content/themes/newsportal-magazine/style.css?ver=1.0.3
h2
3767.3820001073
3888.4060001001
1816
5737
200
text/css
Stylesheet
https://southafricajournal.com/wp-content/themes/eggnews/assets/css/eggnews-responsive.css?ver=1.0.3
h2
3767.7020002156
4042.8480000701
1904
6479
200
text/css
Stylesheet
https://southafricajournal.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
h2
3767.9169999901
4212.3370000627
31331
89496
200
application/x-javascript
Script
https://southafricajournal.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.3.2
h2
3768.1960000191
3871.160000097
4582
11224
200
application/x-javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-161195103-6
h2
4239.6019999869
4267.4320000224
36450
90020
200
application/javascript
Script
https://southafricajournal.com/wp-content/uploads/2020/06/cropped-south-africa-journal-op.png
h2
4239.7680000868
4328.9360001218
2593
2225
200
image/png
Image
https://southafricajournal.com/wp-includes/js/wp-emoji-release.min.js?ver=5.7.2
h2
4240.378000075
4648.9630001597
5075
14229
200
application/x-javascript
Script
https://southafricajournal.com/wp-includes/js/dist/vendor/wp-polyfill.min.js?ver=7.4.4
h2
4140.6580000184
4320.0880000368
34656
99310
200
application/x-javascript
Script
https://southafricajournal.com/wp-content/plugins/contact-form-7/includes/js/index.js?ver=5.4.1
h2
4217.7810000721
4319.1560001578
4417
13485
200
application/x-javascript
Script
https://southafricajournal.com/wp-content/themes/newsportal-magazine/assets/js/jquery.easytabs.js?ver=1.0.0
h2
4238.7420001905
4477.0330002066
7327
27507
200
application/x-javascript
Script
https://southafricajournal.com/wp-content/themes/newsportal-magazine/assets/js/main.js?ver=1.0.0
h2
4238.8970002066
4328.6570000928
572
202
200
application/x-javascript
Script
https://southafricajournal.com/wp-content/themes/eggnews/assets/lib/bxslider/jquery.bxslider.min.js?ver=4.2.12
h2
4239.0650000889
4477.3490000516
6593
23714
200
application/x-javascript
Script
https://southafricajournal.com/wp-content/themes/eggnews/assets/js/custom-script.js?ver=1.0.3
h2
4239.2900001723
4358.4970000666
1701
3538
200
application/x-javascript
Script
https://southafricajournal.com/wp-includes/js/wp-embed.min.js?ver=5.7.2
h2
4239.4310000818
4332.3230000678
1176
1426
200
application/x-javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-NPNKC5P
h2
4240.5100001488
4267.9810000118
30541
75353
200
application/javascript
Script
https://www.googletagservices.com/tag/js/gpt.js
h2
4240.764999995
4246.7490001582
22031
64364
200
text/javascript
Script
https://southafricajournal.com/wp-content/uploads/2017/08/backgroundimge.jpg
h2
4243.6420000158
4476.5940001234
16599
16228
200
image/jpeg
Image
https://fonts.gstatic.com/s/poppins/v15/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
h2
4244.7590001393
4247.2010001075
8505
7900
200
font/woff2
Font
https://southafricajournal.com/wp-content/themes/eggnews/assets/lib/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0
h2
4262.3470001854
4648.2930001803
77506
77160
200
application/font-woff2
Font
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2021051201.js?31061162
h2
4306.228000205
4316.7420001701
110789
313532
200
text/javascript
Script
https://www.google-analytics.com/analytics.js
h2
4397.9850001633
4402.5590000674
20221
49153
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=1334379121&t=pageview&_s=1&dl=https%3A%2F%2Fsouthafricajournal.com%2F&ul=en-us&de=UTF-8&dt=South%20Africa%20Journal%20-%20Hub%20for%20all%20the%20Latest%20News%20%26%20Updates&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=1510731336&gjid=2033715929&cid=1289416969.1621233628&tid=UA-161195103-6&_gid=1005249462.1621233628&_r=1&gtm=2ou5c1&z=792450722
h2
4445.7350000739
4449.2760000285
625
1
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
3782.244
6.835
3792.626
31.885
4244.638
22.069
4266.718
8.015
4279.542
35.832
4318.713
14.169
4332.891
6.869
4341.867
9.526
4357.116
6.145
4363.281
5.429
4368.722
5.043
4375.361
39.523
4417.006
7.834
4424.972
5.231
4431.779
24.254
4456.435
16.507
4509.278
6.683
4675.98
5.468
4681.766
16.348
4698.322
6.212
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Southafricajournal.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Southafricajournal.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 4 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Southafricajournal.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://southafricajournal.com/wp-content/themes/eggnews/assets/css/eggnews.css?ver=1.0.3
13871
3840
Minify JavaScript — Potential savings of 4 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Southafricajournal.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://southafricajournal.com/wp-content/themes/newsportal-magazine/assets/js/jquery.easytabs.js?ver=1.0.0
7327
3632
Remove unused CSS — Potential savings of 10 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Southafricajournal.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://southafricajournal.com/wp-content/themes/eggnews/assets/css/eggnews.css?ver=1.0.3
13871
10389
Remove unused JavaScript — Potential savings of 108 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2021051201.js?31061162
110789
89284
https://www.googletagmanager.com/gtm.js?id=GTM-NPNKC5P
30541
21646
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Southafricajournal.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://southafricajournal.com/
190
https://southafricajournal.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Southafricajournal.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 465 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2021051201.js?31061162
110789
https://southafricajournal.com/wp-content/themes/eggnews/assets/lib/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0
77506
https://www.googletagmanager.com/gtag/js?id=UA-161195103-6
36450
https://southafricajournal.com/wp-includes/js/dist/vendor/wp-polyfill.min.js?ver=7.4.4
34656
https://southafricajournal.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
31331
https://www.googletagmanager.com/gtm.js?id=GTM-NPNKC5P
30541
https://www.googletagservices.com/tag/js/gpt.js
22031
https://www.google-analytics.com/analytics.js
20221
https://southafricajournal.com/wp-content/uploads/2017/08/backgroundimge.jpg
16599
https://southafricajournal.com/
16459
Uses efficient cache policy on static assets — 1 resource found
Southafricajournal.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20221
Avoids an excessive DOM size — 717 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
717
Maximum DOM Depth
14
Maximum Child Elements
77
Avoid chaining critical requests — 16 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Southafricajournal.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 1 user timing
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
gpt-tag-load
Mark
4422.804
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://southafricajournal.com/
133.758
32.157
3.167
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
158.487
Style & Layout
57.939
Other
47.419
Script Parsing & Compilation
31.54
Rendering
20.763
Parse HTML & CSS
17.456
Garbage Collection
2.285
Keep request counts low and transfer sizes small — 29 requests • 465 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
29
476613
Script
15
317462
Font
2
86011
Stylesheet
7
36602
Image
2
19192
Document
1
16459
Other
2
887
Media
0
0
Third-party
8
230314
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
132820
0
66991
0
20846
0
9657
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Opportunities

Eliminate render-blocking resources — Potential savings of 420 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Southafricajournal.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Poppins&ver=5.7.2
1152
230
https://southafricajournal.com/wp-content/themes/eggnews/assets/css/eggnews.css?ver=1.0.3
13871
80

Metrics

Speed Index — 2.9 s
The time taken for the page contents to be visibly populated.

Opportunities

Reduce initial server response time — Root document took 3,560 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://southafricajournal.com/
3562.4

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/poppins/v15/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
2.4419999681413
https://southafricajournal.com/wp-content/themes/eggnews/assets/lib/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0
385.94599999487
96

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of southafricajournal.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Southafricajournal.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
93

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that southafricajournal.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
WordPress
5.7.2
core-js
core-js-global@2.6.11
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://southafricajournal.com/
Allowed
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for southafricajournal.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of southafricajournal.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

robots.txt is not valid — 1 error found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
13
Disallow: ?comments=*
Pattern should either be empty, start with "/" or "*"

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
45

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of southafricajournal.com. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of southafricajournal.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 81
Performance 81
Accessibility 96
Best Practices 87
SEO 91
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
81

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for southafricajournal.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 290 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.082
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Estimated Input Latency — 20 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive southafricajournal.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://southafricajournal.com/
http/1.1
0
83.253999997396
250
0
301
text/html
https://southafricajournal.com/
h2
83.861999970395
857.94799996074
16459
98379
200
text/html
Document
https://southafricajournal.com/wp-includes/css/dist/block-library/style.min.css?ver=5.7.2
h2
874.12900000345
968.47500000149
9082
58171
200
text/css
Stylesheet
https://southafricajournal.com/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=5.4.1
h2
874.71999996342
964.71199998632
1327
2640
200
text/css
Stylesheet
https://southafricajournal.com/wp-content/themes/eggnews/assets/lib/font-awesome/css/font-awesome.min.css?ver=4.7.0
h2
874.85899997409
972.92099997867
7450
31000
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Poppins&ver=5.7.2
h2
874.98999998206
888.49599997047
1152
1020
200
text/css
Stylesheet
https://southafricajournal.com/wp-content/themes/eggnews/assets/css/eggnews.css?ver=1.0.3
h2
875.17299997853
1050.4739999888
13871
76924
200
text/css
Stylesheet
https://southafricajournal.com/wp-content/themes/newsportal-magazine/style.css?ver=1.0.3
h2
875.29299996095
1007.1710000047
1816
5737
200
text/css
Stylesheet
https://southafricajournal.com/wp-content/themes/eggnews/assets/css/eggnews-responsive.css?ver=1.0.3
h2
875.44299999718
966.7419999605
1904
6479
200
text/css
Stylesheet
https://southafricajournal.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
h2
875.76600001194
1202.2069999948
31331
89496
200
application/x-javascript
Script
https://southafricajournal.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.3.2
h2
875.88100001449
964.37599998899
4582
11224
200
application/x-javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-161195103-6
h2
1229.8929999815
1247.8540000156
36429
90020
200
application/javascript
Script
https://southafricajournal.com/wp-content/uploads/2020/06/cropped-south-africa-journal-op.png
h2
1230.0800000085
1322.5380000076
2593
2225
200
image/png
Image
https://southafricajournal.com/wp-includes/js/wp-emoji-release.min.js?ver=5.7.2
h2
1230.2969999728
1323.4539999976
5075
14229
200
application/x-javascript
Script
https://southafricajournal.com/wp-includes/js/dist/vendor/wp-polyfill.min.js?ver=7.4.4
h2
1052.0619999734
1436.314999999
34656
99310
200
application/x-javascript
Script
https://southafricajournal.com/wp-content/plugins/contact-form-7/includes/js/index.js?ver=5.4.1
h2
1209.5759999938
1435.7050000108
4417
13485
200
application/x-javascript
Script
https://southafricajournal.com/wp-content/themes/newsportal-magazine/assets/js/jquery.easytabs.js?ver=1.0.0
h2
1229.0940000094
1323.0709999916
7327
27507
200
application/x-javascript
Script
https://southafricajournal.com/wp-content/themes/newsportal-magazine/assets/js/main.js?ver=1.0.0
h2
1229.2819999857
1318.4769999934
572
202
200
application/x-javascript
Script
https://southafricajournal.com/wp-content/themes/eggnews/assets/lib/bxslider/jquery.bxslider.min.js?ver=4.2.12
h2
1229.4869999751
1320.8929999964
6593
23714
200
application/x-javascript
Script
https://southafricajournal.com/wp-content/themes/eggnews/assets/js/custom-script.js?ver=1.0.3
h2
1229.617999983
1435.3709999705
1701
3538
200
application/x-javascript
Script
https://southafricajournal.com/wp-includes/js/wp-embed.min.js?ver=5.7.2
h2
1229.7769999714
1318.9290000009
1176
1426
200
application/x-javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-NPNKC5P
h2
1230.9679999598
1246.0950000095
30544
75353
200
application/javascript
Script
https://www.googletagservices.com/tag/js/gpt.js
h2
1231.2249999959
1260.2769999648
21914
64012
200
text/javascript
Script
https://southafricajournal.com/wp-content/uploads/2017/08/backgroundimge.jpg
h2
1234.96599996
1399.225000001
16599
16228
200
image/jpeg
Image
https://fonts.gstatic.com/s/poppins/v15/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
h2
1235.8729999978
1238.6829999741
8463
7900
200
font/woff2
Font
https://southafricajournal.com/wp-content/themes/eggnews/assets/lib/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0
h2
1252.5049999822
1632.0139999734
77506
77160
200
application/font-woff2
Font
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2021051001.js?31061140
h2
1314.9569999659
1324.9829999986
109968
310686
200
text/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1360.3109999676
1364.7149999742
20199
49153
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=362634952&t=pageview&_s=1&dl=https%3A%2F%2Fsouthafricajournal.com%2F&ul=en-us&de=UTF-8&dt=South%20Africa%20Journal%20-%20Hub%20for%20all%20the%20Latest%20News%20%26%20Updates&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=1296223946&gjid=500332938&cid=1265080359.1621233643&tid=UA-161195103-6&_gid=1023603011.1621233643&_r=1&gtm=2ou5c1&z=955450700
h2
1390.1479999768
1393.6889999895
625
1
200
text/plain
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
888.021
7.407
900.383
43.8
1236.559
20.86
1257.433
8.462
1270.239
40.452
1321.385
6.702
1328.108
13.74
1341.864
9.042
1353.632
7.506
1361.636
12.336
1379.368
7.927
1397.518
20.006
1417.897
25.776
1470.494
52.843
1660.543
26.375
1686.939
7.434
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Southafricajournal.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Southafricajournal.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 4 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Southafricajournal.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://southafricajournal.com/wp-content/themes/eggnews/assets/css/eggnews.css?ver=1.0.3
13871
3840
Minify JavaScript — Potential savings of 4 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Southafricajournal.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://southafricajournal.com/wp-content/themes/newsportal-magazine/assets/js/jquery.easytabs.js?ver=1.0.0
7327
3632
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Southafricajournal.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://southafricajournal.com/
630
https://southafricajournal.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Southafricajournal.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 464 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2021051001.js?31061140
109968
https://southafricajournal.com/wp-content/themes/eggnews/assets/lib/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0
77506
https://www.googletagmanager.com/gtag/js?id=UA-161195103-6
36429
https://southafricajournal.com/wp-includes/js/dist/vendor/wp-polyfill.min.js?ver=7.4.4
34656
https://southafricajournal.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
31331
https://www.googletagmanager.com/gtm.js?id=GTM-NPNKC5P
30544
https://www.googletagservices.com/tag/js/gpt.js
21914
https://www.google-analytics.com/analytics.js
20199
https://southafricajournal.com/wp-content/uploads/2017/08/backgroundimge.jpg
16599
https://southafricajournal.com/
16459
Uses efficient cache policy on static assets — 1 resource found
Southafricajournal.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20199
Avoids an excessive DOM size — 717 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
717
Maximum DOM Depth
14
Maximum Child Elements
77
Avoid chaining critical requests — 16 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Southafricajournal.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 1 user timing
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
gpt-tag-load
Mark
1410.323
JavaScript execution time — 0.8 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://southafricajournal.com/
659.956
193.328
13.124
https://southafricajournal.com/wp-includes/js/dist/vendor/wp-polyfill.min.js?ver=7.4.4
149.496
131.376
10.792
Unattributable
106.208
3.34
0.5
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2021051001.js?31061140
105.864
70.952
28.296
https://www.googletagservices.com/tag/js/gpt.js
101.856
60.752
37.88
https://www.google-analytics.com/analytics.js
84.36
73.576
5.212
https://southafricajournal.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
77.6
65.252
6.86
https://www.googletagmanager.com/gtm.js?id=GTM-NPNKC5P
73.852
32.656
7.92
https://www.googletagmanager.com/gtag/js?id=UA-161195103-6
65.416
51.516
10.236
Minimizes main-thread work — 1.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
701.444
Style & Layout
278.516
Other
221.952
Script Parsing & Compilation
140.416
Rendering
88.964
Parse HTML & CSS
77.468
Keep request counts low and transfer sizes small — 29 requests • 464 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
29
475581
Script
15
316484
Font
2
85969
Stylesheet
7
36602
Image
2
19192
Document
1
16459
Other
2
875
Media
0
0
Third-party
8
229294
Minimize third-party usage — Third-party code blocked the main thread for 40 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
20824
20.644
131882
17.384
66973
0
9615
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.054518663760811
div
0.015457902255073
div
0.01077236247804
0.0011260271072388
a
0.00036349826388889
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 8 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://southafricajournal.com/wp-includes/js/dist/vendor/wp-polyfill.min.js?ver=7.4.4
4428
211
https://southafricajournal.com/
1260
175
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2021051001.js?31061140
5808
103
https://southafricajournal.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
3210
83
https://southafricajournal.com/
1452
81
https://www.google-analytics.com/analytics.js
3777
80
https://www.googletagservices.com/tag/js/gpt.js
4373
55
https://www.googletagmanager.com/gtm.js?id=GTM-NPNKC5P
5911
53
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 2.8 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 4.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 3.0 s
The timing of the largest text or image that is painted.
Time to Interactive — 6.0 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 6.1 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 210 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.8 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 5520 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Remove unused CSS — Potential savings of 10 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Southafricajournal.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://southafricajournal.com/wp-content/themes/eggnews/assets/css/eggnews.css?ver=1.0.3
13871
10431
Remove unused JavaScript — Potential savings of 108 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://securepubads.g.doubleclick.net/gpt/pubads_impl_2021051001.js?31061140
109968
88529
https://www.googletagmanager.com/gtm.js?id=GTM-NPNKC5P
30544
21648

Opportunities

Eliminate render-blocking resources — Potential savings of 1,370 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Southafricajournal.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Poppins&ver=5.7.2
1152
780
https://southafricajournal.com/wp-content/themes/eggnews/assets/css/eggnews.css?ver=1.0.3
13871
150
https://southafricajournal.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
31331
450
Reduce initial server response time — Root document took 780 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://southafricajournal.com/
775.083

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/poppins/v15/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
2.8099999763072
https://southafricajournal.com/wp-content/themes/eggnews/assets/lib/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0
379.50899999123
96

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of southafricajournal.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Southafricajournal.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that southafricajournal.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
WordPress
5.7.2
core-js
core-js-global@2.6.11
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://southafricajournal.com/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://southafricajournal.com/wp-content/uploads/2020/06/cropped-south-africa-journal-op.png
178 x 90
220 x 111
356 x 180
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for southafricajournal.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of southafricajournal.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

robots.txt is not valid — 1 error found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
13
Disallow: ?comments=*
Pattern should either be empty, start with "/" or "*"

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
50

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of southafricajournal.com. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of southafricajournal.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 198.54.116.97
Continent: North America
Country: United States
United States Flag
Region: Arizona
City: Queen Creek
Longitude: -111.6343
Latitude: 33.2487
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Namecheap, Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NAMECHEAP INC 104.16.99.56
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: southafricajournal.com
Issued By: Sectigo RSA Domain Validation Secure Server CA
Valid From: 10th November, 2020
Valid To: 3rd December, 2021
Subject: CN = southafricajournal.com
Hash: c86368ee
Issuer: CN = Sectigo RSA Domain Validation Secure Server CA
O = Sectigo Limited
S = GB
Version: 2
Serial Number: 0xC0B86674495C7735E58700EE98BE1285
Serial Number (Hex): C0B86674495C7735E58700EE98BE1285
Valid From: 10th November, 2024
Valid To: 3rd December, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.7
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.1

Authority Information Access: CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
OCSP - URI:http://ocsp.sectigo.com

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Nov 10 09:52:51.232 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:40:32:7C:53:1B:DD:6D:CE:DC:2A:35:58:
EE:16:35:11:95:F9:6A:23:95:7E:72:B0:C1:4C:64:E5:
67:34:D1:4C:02:20:63:54:93:F7:9C:A9:50:DA:9F:07:
28:75:DC:54:CE:6A:D1:C5:28:B6:DB:D5:5C:AB:73:CF:
D0:9B:ED:07:0E:DF
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
Timestamp : Nov 10 09:52:51.272 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:17:0E:2E:5D:B2:2F:76:71:F7:E8:1A:5C:
88:BA:92:62:E1:37:E9:8D:F7:40:4E:FA:01:76:63:01:
3E:BA:AD:E6:02:21:00:99:5F:09:5E:8F:FE:28:13:8D:
FE:FA:1A:FD:4B:5B:DC:04:F5:60:26:0E:6A:3E:4E:26:
16:92:DA:BF:71:1D:55
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.southafricajournal.com
DNS:southafricajournal.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 301 Moved Permanently
date: 17th May, 2021
server: Apache
content-type: text/html; charset=iso-8859-1
location: https://southafricajournal.com/

Whois Lookup

Created: 16th February, 2015
Changed: 24th January, 2019
Expires: 16th February, 2022
Registrar: NAMECHEAP INC
Status: clientTransferProhibited
Nameservers: dns1.namecheaphosting.com
dns2.namecheaphosting.com
Owner Name: Withheld for Privacy Purposes
Owner Organization: Privacy service provided by Withheld for Privacy ehf
Owner Street: Kalkofnsvegur 2
Owner Post Code: 101
Owner City: Reykjavik
Owner State: Capital Region
Owner Country: IS
Owner Phone: +354.4212434
Owner Email: d8cd6a1243a547fe8f7d4aae66889077.protect@withheldforprivacy.com
Admin Name: Withheld for Privacy Purposes
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2
Admin Post Code: 101
Admin City: Reykjavik
Admin State: Capital Region
Admin Country: IS
Admin Phone: +354.4212434
Admin Email: d8cd6a1243a547fe8f7d4aae66889077.protect@withheldforprivacy.com
Tech Name: Withheld for Privacy Purposes
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2
Tech Post Code: 101
Tech City: Reykjavik
Tech State: Capital Region
Tech Country: IS
Tech Phone: +354.4212434
Tech Email: d8cd6a1243a547fe8f7d4aae66889077.protect@withheldforprivacy.com
Full Whois: Domain name: southafricajournal.com
Registry Domain ID: 1903251891_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2019-01-24T11:12:17.63Z
Creation Date: 2015-02-16T11:39:39.00Z
Registrar Registration Expiration Date: 2022-02-16T11:39:39.00Z
Registrar: NAMECHEAP INC
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Reseller: NAMECHEAP INC
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Withheld for Privacy Purposes
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: Kalkofnsvegur 2
Registrant City: Reykjavik
Registrant State/Province: Capital Region
Registrant Postal Code: 101
Registrant Country: IS
Registrant Phone: +354.4212434
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: d8cd6a1243a547fe8f7d4aae66889077.protect@withheldforprivacy.com
Registry Admin ID:
Admin Name: Withheld for Privacy Purposes
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2
Admin City: Reykjavik
Admin State/Province: Capital Region
Admin Postal Code: 101
Admin Country: IS
Admin Phone: +354.4212434
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: d8cd6a1243a547fe8f7d4aae66889077.protect@withheldforprivacy.com
Registry Tech ID:
Tech Name: Withheld for Privacy Purposes
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2
Tech City: Reykjavik
Tech State/Province: Capital Region
Tech Postal Code: 101
Tech Country: IS
Tech Phone: +354.4212434
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: d8cd6a1243a547fe8f7d4aae66889077.protect@withheldforprivacy.com
Name Server: dns1.namecheaphosting.com
Name Server: dns2.namecheaphosting.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-05-16T07:40:21.11Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

Nameservers

Name IP Address
dns1.namecheaphosting.com 156.154.132.200
dns2.namecheaphosting.com 156.154.133.200
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$1,785 USD 1/5
$774 USD 1/5
$844 USD 1/5