Access v2.nativebase.io. NativeBase | Essential cross-platform UI components for React Native

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value38.7 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value2,580 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value31.2 s

0/100

10%

v2.nativebase.io

687 ms

2uecR3KJSBminRxNPrcYszMsujk.js

23 ms

font-awesome.min.css

24 ms

css

29 ms

app.css

887 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 38% of them (39 requests) were addressed to the original V2.nativebase.io, 24% (24 requests) were made to Geekyants.com and 14% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Slack.nativebase.io.

Content Size

3.0 MB

After Optimization

2.7 MB

In fact, the total size of V2.nativebase.io main page is 3.0 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. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 37.7 kB

Original 47.7 kB
After minification 47.1 kB
After compression 10.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. 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 37.7 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 140.0 kB

Original 2.6 MB
After minification 2.5 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. V 2 Native Base images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 103.9 kB

Original 299.0 kB
After minification 294.5 kB
After compression 195.1 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 103.9 kB or 35% of the original size.

CSS Optimization

-2%

Potential reduce by 685 B

Original 35.5 kB
After minification 35.5 kB
After compression 34.8 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. V2.nativebase.io has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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/).

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 V2.nativebase.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 V2.nativebase.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

v2.nativebase.io

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

Report Summary

Performance

Accessibility

Best Practices

SEO

NativeBase | Essential cross-platform UI components for React Native

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

v2.nativebase.io

2uecR3KJSBminRxNPrcYszMsujk.js

font-awesome.min.css

css

app.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

v2.nativebase.io

2uecR3KJSBminRxNPrcYszMsujk.js

font-awesome.min.css

css

app.css

prism.css

css

front-page-icon.png

app.js

mc-validate.js

2783286.js

Slack_Icon.png

slack.nativebase.io

geekyants.com

iOS.gif

Android.gif

BG.jpg

rsz_logo300.png

With%20and%20Without%20NativeBase.png

slider-1.png

appstore.png

expo.png

image.png

list-Icon.png

list-Icon%202.png

Input.png

Input%202.png

Button.png

Button%202.png

Header.png

Header%202.png

Banner1-V2.png

Banner-V2.png

quote1.png

quote2.png

tilr.png

flynance.png

olympics.png

sols.png

raccoone.png

texi-app-icon.png

dating.png

dynamicstore.png