Tools & Wizards About Us
weedarr.wikidot.com screenshot

Report Summary

  • 77

    Performance

    Renders faster than
    85% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

weedarr.wikidot.com

Welcome - Gta sa-mp resources site

Page Load Speed

950 ms in total

First Response

103 ms

Resources Loaded

755 ms

Page Rendered

92 ms

weedarr.wikidot.com screenshot

About Website

Click here to check amazing Weedarr Wikidot content for United States. Otherwise, check out these important facts you probably never knew about weedarr.wikidot.com

Visit weedarr.wikidot.com

Key Findings

We analyzed Weedarr.wikidot.com page load time and found that the first response time was 103 ms and then it took 847 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

weedarr.wikidot.com performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value2.5 s

97/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

78/100

10%

Network Requests Diagram

weedarr.wikidot.com

103 ms

gpt.js

7 ms

init.combined.js

15 ms

WIKIDOT.combined.js

12 ms

pubads_impl_82.js

64 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Weedarr.wikidot.com, 16% (5 requests) were made to D3g0gp89917ko0.cloudfront.net and 16% (5 requests) were made to Weedarr.wdfiles.com. The less responsive or slowest element that took the longest time to load (525 ms) relates to the external source A.getgamers.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 419.7 kB (63%)

Content Size

662.4 kB

After Optimization

242.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weedarr.wikidot.com main page is 662.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 625.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 16.2 kB

  • Original 21.0 kB
  • After minification 18.6 kB
  • After compression 4.8 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 2.4 kB, which is 11% 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 16.2 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 158 B
  • After minification 158 B

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. Weedarr Wikidot images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 396.8 kB

  • Original 625.0 kB
  • After minification 623.3 kB
  • After compression 228.2 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 396.8 kB or 63% of the original size.

CSS Optimization

-41%

Potential reduce by 6.7 kB

  • Original 16.3 kB
  • After minification 15.1 kB
  • After compression 9.5 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. Weedarr.wikidot.com needs all CSS files to be minified and compressed as it can save up to 6.7 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (60%)

Requests Now

30

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weedarr.wikidot.com

weedarr.wikidot.com

103 ms

gpt.js

gpt.js

7 ms

init.combined.js

init.combined.js

15 ms

WIKIDOT.combined.js

WIKIDOT.combined.js

12 ms

pubads_impl_82.js

pubads_impl_82.js

64 ms

style.css

style.css

19 ms

style.css

style.css

22 ms

style.css

style.css

24 ms

container.html

container.html

52 ms

banner.gif

banner.gif

46 ms

156 ms

ads

ads

89 ms

dc.js

dc.js

56 ms

quant.js

quant.js

23 ms

vglnk.js

vglnk.js

26 ms

a.getgamers.eu

a.getgamers.eu

525 ms

ajax-module-connector.php

ajax-module-connector.php

30 ms

small.png

small.png

65 ms

vsmall.png

vsmall.png

64 ms

300x50.png

300x50.png

506 ms

logo1.jpg

logo1.jpg

26 ms

pixel;r=1282106623;a=p-edL3gsnUjJzw-;fpan=1;fpa=P0-535535746-1458465283678;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458465283678;tzo=-180;ref=;url=http%3A%2F%2Fweedarr.wikidot.com%2F;ogl=

pixel;r=1282106623;a=p-edL3gsnUjJzw-;fpan=1;fpa=P0-535535746-1458465283678;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458465283678;tzo=-180;ref=;url=http%3A%2F%2Fweedarr.wikidot.com%2F;ogl=

16 ms

pixel.gif

pixel.gif

5 ms

pixel.gif

pixel.gif

5 ms

__utm.gif

__utm.gif

49 ms

__utm.gif

__utm.gif

53 ms

ads

ads

36 ms

osd.js

osd.js

9 ms

ads

ads

394 ms

bounce

bounce

16 ms

bounce

bounce

375 ms

Accessibility Review

weedarr.wikidot.com accessibility score

66

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.

Names and labels

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

Impact

Issue

High

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

weedarr.wikidot.com best practices score

58

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

weedarr.wikidot.com SEO score

69

Search Engine Optimization Advices

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 Weedarr.wikidot.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 Weedarr.wikidot.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

weedarr.wikidot.com

Open Graph description is not detected on the main page of Weedarr Wikidot. 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: