Tools & Wizards About Us

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

slash.ng

Page Load Speed

10.9 sec in total

First Response

5 sec

Resources Loaded

5.4 sec

Page Rendered

573 ms

About Website

Visit slash.ng now to see the best up-to-date Slash content and also check out these interesting facts you probably never knew about slash.ng

Buy all your favorite items such as phones, electronics, cloths, laptops, bags, shoes.. in Nigeria on slash marketplace from verified wholesalers & suppliers near you.

Visit slash.ng

Key Findings

We analyzed Slash.ng page load time and found that the first response time was 5 sec and then it took 6 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

slash.ng performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

Network Requests Diagram

slash.ng

4974 ms

bootstrap.min.css

53 ms

font-awesome.min.css

38 ms

css2

39 ms

custom.css

211 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 74% of them (40 requests) were addressed to the original Slash.ng, 7% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Slash.ng.

Page Optimization Overview & Recommendations

Page size can be reduced by 455.4 kB (35%)

Content Size

1.3 MB

After Optimization

863.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Slash.ng main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 194.5 kB

  • Original 212.7 kB
  • After minification 143.8 kB
  • After compression 18.2 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 69.0 kB, which is 32% 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 194.5 kB or 91% of the original size.

Image Optimization

-24%

Potential reduce by 259.0 kB

  • Original 1.1 MB
  • After minification 814.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. Obviously, Slash needs image optimization as it can save up to 259.0 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 883 B

  • Original 27.3 kB
  • After minification 27.3 kB
  • After compression 26.4 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

-20%

Potential reduce by 989 B

  • Original 4.9 kB
  • After minification 4.9 kB
  • After compression 3.9 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. Slash.ng needs all CSS files to be minified and compressed as it can save up to 989 B or 20% of the original size.

Requests Breakdown

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

Requests Now

48

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

slash.ng accessibility score

94

Accessibility Issues

Internationalization and localization

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

Impact

Issue

High

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

Best Practices

slash.ng 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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

slash.ng SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Slash.ng can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Slash.ng main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

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