Report Summary

  • 87

    Performance

    Renders faster than
    89% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

dokuwikispatial.sourceforge.io

Dokuwiki Spatial [Dokuwikispatial]

Page Load Speed

1.9 sec in total

First Response

109 ms

Resources Loaded

1.7 sec

Page Rendered

102 ms

dokuwikispatial.sourceforge.io screenshot

About Website

Visit dokuwikispatial.sourceforge.io now to see the best up-to-date Dokuwiki Spatial Sourceforge content for China and also check out these interesting facts you probably never knew about dokuwikispatial.sourceforge.io

Dokuwiki Spatial [logo ] Dokuwiki Spatial provides spatial extensions for DokuWiki. Currently we have: * Openlayersmap plugin to add maps to your wiki. * mbtiles to use local basemaps stored in ...

Visit dokuwikispatial.sourceforge.io

Key Findings

We analyzed Dokuwikispatial.sourceforge.io page load time and found that the first response time was 109 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

dokuwikispatial.sourceforge.io performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

79/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.171

70/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

dokuwikispatial.sourceforge.io

109 ms

start

184 ms

css.php

277 ms

jquery.min.js

23 ms

jquery-ui.min.js

33 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 85% of them (22 requests) were addressed to the original Dokuwikispatial.sourceforge.io, 8% (2 requests) were made to Cdnjs.cloudflare.com and 8% (2 requests) were made to Openhub.net. The less responsive or slowest element that took the longest time to load (858 ms) belongs to the original domain Dokuwikispatial.sourceforge.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 18.9 kB (55%)

Content Size

34.5 kB

After Optimization

15.6 kB

In fact, the total size of Dokuwikispatial.sourceforge.io main page is 34.5 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. 20% of websites need less resources to load. HTML takes 22.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 18.3 kB

  • Original 22.9 kB
  • After minification 21.3 kB
  • After compression 4.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 18.3 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 134 B

  • Original 7.7 kB
  • After minification 7.6 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. Dokuwiki Spatial Sourceforge images are well optimized though.

CSS Optimization

-13%

Potential reduce by 496 B

  • Original 3.9 kB
  • After minification 3.9 kB
  • After compression 3.4 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. Dokuwikispatial.sourceforge.io needs all CSS files to be minified and compressed as it can save up to 496 B or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (57%)

Requests Now

23

After Optimization

10

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dokuwiki Spatial Sourceforge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Accessibility Review

dokuwikispatial.sourceforge.io accessibility score

98

Accessibility Issues

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

dokuwikispatial.sourceforge.io best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dokuwikispatial.sourceforge.io SEO score

88

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Dokuwikispatial.sourceforge.io 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 Dokuwikispatial.sourceforge.io 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 PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: