Access nasti.co.za. Nasti

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.449

20/100

15%

TTI (Time to Interactive)

Value5.4 s

71/100

10%

nasti.co.za

759 ms

libasync.js

179 ms

mobile-detect.min.js

30 ms

logo.gif

1601 ms

wa1.png

931 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 60% of them (3 requests) were addressed to the original Nasti.co.za, 20% (1 request) were made to Rtcdn.cincopa.com and 20% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Nasti.co.za.

Content Size

70.3 kB

After Optimization

61.7 kB

In fact, the total size of Nasti.co.za main page is 70.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 64.7 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 3.4 kB

Original 5.6 kB
After minification 5.6 kB
After compression 2.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 3.4 kB or 60% of the original size.

Image Optimization

-8%

Potential reduce by 5.2 kB

Original 64.7 kB
After minification 59.5 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. Nasti images are well optimized though.

Requests Now

After Optimization

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nasti. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nasti.co.za can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nasti.co.za main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Nasti. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: