Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

neveo.io

Neveo – The monthly photo journal for your grandparents

Page Load Speed

2.5 sec in total

First Response

31 ms

Resources Loaded

1.6 sec

Page Rendered

873 ms

neveo.io screenshot

About Website

Visit neveo.io now to see the best up-to-date Neveo content for United States and also check out these interesting facts you probably never knew about neveo.io

The monthly photo journal for grandparents. You and the other family members upload your photos to the Neveo app and at the end of the month Neveo prints your family journal and sends it to your grand...

Visit neveo.io

Key Findings

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

Performance Metrics

neveo.io performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value60.1 s

0/100

25%

SI (Speed Index)

Value21.0 s

0/100

10%

TBT (Total Blocking Time)

Value14,340 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.418

23/100

15%

TTI (Time to Interactive)

Value50.2 s

0/100

10%

Network Requests Diagram

neveo.io

31 ms

neveo.io

32 ms

language-storage.js

17 ms

initial-language-redirect.js

241 ms

feather.css

42 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 80% of them (72 requests) were addressed to the original Neveo.io, 4% (4 requests) were made to Google-analytics.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Neveo.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (13%)

Content Size

8.7 MB

After Optimization

7.6 MB

In fact, the total size of Neveo.io main page is 8.7 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. 85% 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. Images take 8.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 82.3 kB

  • Original 96.3 kB
  • After minification 78.0 kB
  • After compression 14.0 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 18.3 kB, which is 19% 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 82.3 kB or 85% of the original size.

Image Optimization

-9%

Potential reduce by 707.8 kB

  • Original 8.2 MB
  • After minification 7.4 MB

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

JavaScript Optimization

-65%

Potential reduce by 115.7 kB

  • Original 178.0 kB
  • After minification 168.0 kB
  • After compression 62.3 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 115.7 kB or 65% of the original size.

CSS Optimization

-85%

Potential reduce by 265.3 kB

  • Original 313.5 kB
  • After minification 309.7 kB
  • After compression 48.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. Neveo.io needs all CSS files to be minified and compressed as it can save up to 265.3 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

83

After Optimization

36

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

Accessibility Review

neveo.io accessibility score

80

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

neveo.io best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

neveo.io SEO score

79

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

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Neveo.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 Neveo.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 Neveo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: