Tools & Wizards About Us
help.nativex.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

help.nativex.com

Mobile Advertising Company | App Marketing Agency | Nativex

Page Load Speed

2.8 sec in total

First Response

532 ms

Resources Loaded

2.2 sec

Page Rendered

140 ms

help.nativex.com screenshot

About Website

Click here to check amazing Help Nativex content for China. Otherwise, check out these important facts you probably never knew about help.nativex.com

Nativex is an app marketing agency dedicated to driving ROI for all sectors of business in a mobile-first world. Contact us today to get started!

Visit help.nativex.com

Key Findings

We analyzed Help.nativex.com page load time and found that the first response time was 532 ms and then it took 2.3 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

help.nativex.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value28.7 s

0/100

25%

SI (Speed Index)

Value19.0 s

0/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value33.5 s

0/100

10%

Network Requests Diagram

help.nativex.com

532 ms

batch.css

386 ms

batch.css

456 ms

batch.css

296 ms

confluence.extra.livesearch:livesearch-macro-web-resources.css

298 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 93% of them (28 requests) were addressed to the original Help.nativex.com, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (947 ms) belongs to the original domain Help.nativex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.2 kB (67%)

Content Size

95.0 kB

After Optimization

31.8 kB

  • HTML
  • JavaScript

In fact, the total size of Help.nativex.com main page is 95.0 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. 25% of websites need less resources to load. HTML takes 74.0 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 63.1 kB

  • Original 74.0 kB
  • After minification 57.4 kB
  • After compression 10.9 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 16.6 kB, which is 22% 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 63.1 kB or 85% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 10 (36%)

Requests Now

28

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

help.nativex.com

help.nativex.com

532 ms

batch.css

batch.css

386 ms

batch.css

batch.css

456 ms

batch.css

batch.css

296 ms

confluence.extra.livesearch:livesearch-macro-web-resources.css

confluence.extra.livesearch:livesearch-macro-web-resources.css

298 ms

colors.css

colors.css

281 ms

custom.css

custom.css

297 ms

batch.js

batch.js

947 ms

batch.js

batch.js

829 ms

batch.js

batch.js

441 ms

confluence.extra.livesearch:livesearch-macro-web-resources.js

confluence.extra.livesearch:livesearch-macro-web-resources.js

429 ms

link-preview-confluence.js

link-preview-confluence.js

475 ms

analytics.js

analytics.js

134 ms

atl.site.logo

atl.site.logo

140 ms

global.logo

global.logo

236 ms

icon_monetization.png

icon_monetization.png

181 ms

icon_acquireusers.png

icon_acquireusers.png

182 ms

knowledge-base-icon.png

knowledge-base-icon.png

183 ms

appswitcher

appswitcher

119 ms

atlassian-icons.woff

atlassian-icons.woff

352 ms

sidebar-shadow.png

sidebar-shadow.png

196 ms

vgrabber.gif

vgrabber.gif

198 ms

b11350553b66d8992d3273f7fa63b6e2

b11350553b66d8992d3273f7fa63b6e2

182 ms

naturalchildren.action

naturalchildren.action

204 ms

naturalchildren.action

naturalchildren.action

233 ms

naturalchildren.action

naturalchildren.action

243 ms

naturalchildren.action

naturalchildren.action

269 ms

externallinks.action

externallinks.action

265 ms

likes

likes

315 ms

collect

collect

15 ms

Accessibility Review

help.nativex.com accessibility score

66

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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

Tables and lists

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

Impact

Issue

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

help.nativex.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

help.nativex.com SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Help.nativex.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Help.nativex.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

help.nativex.com

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