Tools & Wizards About Us
weetracker.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

weetracker.com

WeeTracker - Business, Startups & Economy News From Africa

Page Load Speed

6.2 sec in total

First Response

54 ms

Resources Loaded

5.5 sec

Page Rendered

613 ms

weetracker.com screenshot

About Website

Visit weetracker.com now to see the best up-to-date Wee Tracker content for Nigeria and also check out these interesting facts you probably never knew about weetracker.com

WeeTracker is a premium publication that covers the African digital and startup ecosystem with groundbreaking original journalism. Find the most relevant narratives, analysis, data and more in one pla...

Visit weetracker.com

Key Findings

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

weetracker.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value2,880 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.295

40/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

weetracker.com

54 ms

weetracker.com

1557 ms

js

98 ms

bootstrap.min.css

58 ms

wt-new.css

1128 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 47% of them (47 requests) were addressed to the original Weetracker.com, 22% (22 requests) were made to Fonts.gstatic.com and 4% (4 requests) 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 Weetracker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 455.5 kB (29%)

Content Size

1.6 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weetracker.com main page is 1.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 886.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 113.4 kB

  • Original 135.9 kB
  • After minification 135.8 kB
  • After compression 22.6 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 113.4 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 450.7 kB
  • After minification 450.7 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. Wee Tracker images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 336.1 kB

  • Original 886.7 kB
  • After minification 886.7 kB
  • After compression 550.7 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 336.1 kB or 38% of the original size.

CSS Optimization

-7%

Potential reduce by 6.0 kB

  • Original 90.2 kB
  • After minification 90.2 kB
  • After compression 84.2 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. Weetracker.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 56 (79%)

Requests Now

71

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weetracker.com

weetracker.com

54 ms

weetracker.com

weetracker.com

1557 ms

js

js

98 ms

bootstrap.min.css

bootstrap.min.css

58 ms

wt-new.css

wt-new.css

1128 ms

style.css

style.css

53 ms

all.min.css

all.min.css

79 ms

js

js

130 ms

settings.css

settings.css

52 ms

theme.css

theme.css

69 ms

style.min.css

style.min.css

67 ms

frontend.min.css

frontend.min.css

69 ms

frontend.css

frontend.css

83 ms

frontend.min.css

frontend.min.css

83 ms

flatpickr.min.css

flatpickr.min.css

84 ms

select2.min.css

select2.min.css

83 ms

style.basic.css

style.basic.css

122 ms

style-underline.css

style-underline.css

90 ms

tablepress-combined.min.css

tablepress-combined.min.css

91 ms

frontend-gtag.js

frontend-gtag.js

121 ms

jquery.js

jquery.js

125 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

122 ms

frontend.min.js

frontend.min.js

122 ms

flatpickr.min.js

flatpickr.min.js

123 ms

select2.min.js

select2.min.js

124 ms

css

css

82 ms

adsbygoogle.js

adsbygoogle.js

120 ms

a076d05399.js

a076d05399.js

71 ms

form.css

form.css

86 ms

form-embed.js

form-embed.js

121 ms

swiper.min.css

swiper.min.css

124 ms

jquery.min.js

jquery.min.js

34 ms

swiper.min.js

swiper.min.js

12 ms

email-decode.min.js

email-decode.min.js

13 ms

685b6f4a9a.js

685b6f4a9a.js

36 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

20 ms

subsnew-express.min.js

subsnew-express.min.js

18 ms

slick.min.js

slick.min.js

21 ms

subsnew-extra.js

subsnew-extra.js

23 ms

weetrackermain.js

weetrackermain.js

24 ms

frontend.min.js

frontend.min.js

30 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

29 ms

wp-polyfill.min.js

wp-polyfill.min.js

34 ms

hooks.min.js

hooks.min.js

33 ms

jquery.ajaxsearchlite.min.js

jquery.ajaxsearchlite.min.js

36 ms

frontend.min.js

frontend.min.js

37 ms

smush-lazy-load-native.min.js

smush-lazy-load-native.min.js

38 ms

wp-embed.min.js

wp-embed.min.js

41 ms

signup.js

signup.js

47 ms

validate.js

validate.js

47 ms

gtm.js

gtm.js

79 ms

show_ads_impl.js

show_ads_impl.js

77 ms

deepfake_Weetracker.jpg

deepfake_Weetracker.jpg

71 ms

fa-solid-900.ttf

fa-solid-900.ttf

117 ms

fa-regular-400.ttf

fa-regular-400.ttf

116 ms

webfont.js

webfont.js

68 ms

zrt_lookup.html

zrt_lookup.html

295 ms

newsletter-b.jpg

newsletter-b.jpg

96 ms

ads

ads

174 ms

fa-brands-400.ttf

fa-brands-400.ttf

61 ms

diffuser.js

diffuser.js

171 ms

css

css

116 ms

wt-2.png

wt-2.png

120 ms

african-growth-story-new.png

african-growth-story-new.png

124 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8JoA.woff

54 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8JoA.woff

54 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8JoA.woff

56 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXBi8JoA.woff

54 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8JoA.woff

46 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8JoA.woff

55 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQBi8JoA.woff

57 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8JoA.woff

57 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYw.woff

55 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYw.woff

56 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYw.woff

57 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYw.woff

97 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYw.woff

96 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff

98 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtU.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtU.woff

97 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff

98 ms

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

98 ms

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

99 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

99 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

100 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

101 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

101 ms

prism.app-us1.com

prism.app-us1.com

147 ms

marketforce3.jpg

marketforce3.jpg

30 ms

Chptr_weetracker-.jpg

Chptr_weetracker-.jpg

1315 ms

pta_en.js

pta_en.js

49 ms

app.js

app.js

925 ms

sodar

sodar

23 ms

insight.min.js

insight.min.js

24 ms

221028_Dozy_GQ0070-1-scaled-e1711651204392.jpg

221028_Dozy_GQ0070-1-scaled-e1711651204392.jpg

25 ms

insight_tag_errors.gif

insight_tag_errors.gif

103 ms

sodar2.js

sodar2.js

58 ms

52fca612.js

52fca612.js

7 ms

runner.html

runner.html

13 ms

aframe

aframe

37 ms

awBj2nEM4FjaFk3wlyC-mA9dnmiUMLTOhjF5f4M09mQ.js

awBj2nEM4FjaFk3wlyC-mA9dnmiUMLTOhjF5f4M09mQ.js

4 ms

Accessibility Review

weetracker.com accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

weetracker.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

weetracker.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weetracker.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Weetracker.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

weetracker.com

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