Tools & Wizards About Us
docs.neatline.org screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

docs.neatline.org

Neatline for Omeka Classic

Page Load Speed

352 ms in total

First Response

75 ms

Resources Loaded

277 ms

Page Rendered

0 ms

docs.neatline.org screenshot

About Website

Visit docs.neatline.org now to see the best up-to-date Docs Neatline content for United States and also check out these interesting facts you probably never knew about docs.neatline.org

Neatline allows scholars, students, and curators to tell stories with maps and timelines.

Visit docs.neatline.org

Key Findings

We analyzed Docs.neatline.org page load time and found that the first response time was 75 ms and then it took 277 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

docs.neatline.org performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value3.8 s

90/100

10%

Network Requests Diagram

docs.neatline.org

75 ms

css

25 ms

style.css

70 ms

syntax.css

42 ms

neatline-logo-rgb.png

65 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 18% of them (2 requests) were addressed to the original Docs.neatline.org, 36% (4 requests) were made to Neatline.org and 18% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (110 ms) relates to the external source Static.scholarslab.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.0 kB (47%)

Content Size

55.6 kB

After Optimization

29.6 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Docs.neatline.org main page is 55.6 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. Only 5% of websites need less resources to load. CSS take 25.4 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 6.1 kB

  • Original 8.6 kB
  • After minification 7.3 kB
  • After compression 2.5 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 1.4 kB, which is 16% 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 6.1 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 21.6 kB
  • After minification 21.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. Docs Neatline images are well optimized though.

CSS Optimization

-78%

Potential reduce by 19.9 kB

  • Original 25.4 kB
  • After minification 23.4 kB
  • After compression 5.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. Docs.neatline.org needs all CSS files to be minified and compressed as it can save up to 19.9 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

docs.neatline.org

docs.neatline.org

75 ms

css

css

25 ms

style.css

style.css

70 ms

syntax.css

syntax.css

42 ms

neatline-logo-rgb.png

neatline-logo-rgb.png

65 ms

cse.js

cse.js

17 ms

slab-logo-black-200px.png

slab-logo-black-200px.png

110 ms

bg_wrapper.jpg

bg_wrapper.jpg

38 ms

neatline-mark-tan.png

neatline-mark-tan.png

36 ms

cse.js

cse.js

73 ms

jsapi

jsapi

29 ms

Accessibility Review

docs.neatline.org accessibility score

100

Accessibility Issues

Best Practices

docs.neatline.org 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

docs.neatline.org SEO score

89

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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 Docs.neatline.org 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 Docs.neatline.org 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

docs.neatline.org

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