Tools & Wizards About Us
nextcore.co screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    68% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    61% of websites

nextcore.co

Nextcore : LiDAR Drone Technology Built for Simplicity

Page Load Speed

7.3 sec in total

First Response

249 ms

Resources Loaded

3.8 sec

Page Rendered

3.3 sec

nextcore.co screenshot

About Website

Visit nextcore.co now to see the best up-to-date Nextcore content and also check out these interesting facts you probably never knew about nextcore.co

The Nextcore system combines well built hardware with a simple. effective software solution to provide you with survey grade data that's consistent and reliable.

Visit nextcore.co

Key Findings

We analyzed Nextcore.co page load time and found that the first response time was 249 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

nextcore.co performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

nextcore.co

249 ms

www.nextcore.co

571 ms

css2

61 ms

mbw8ebu.css

115 ms

breeze_e6fae855021a88a0067fcc58121c594f.css

83 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 69% of them (46 requests) were addressed to the original Nextcore.co, 7% (5 requests) were made to Use.typekit.net and 3% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Nextcore.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 180.0 kB (6%)

Content Size

2.8 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nextcore.co main page is 2.8 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. 75% 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.7 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 56.1 kB

  • Original 69.1 kB
  • After minification 57.4 kB
  • After compression 13.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 11.7 kB, which is 17% 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 56.1 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 123.7 kB

  • Original 2.7 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. Nextcore images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 134 B

  • Original 56.2 kB
  • After minification 56.2 kB
  • After compression 56.0 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.

CSS Optimization

-0%

Potential reduce by 98 B

  • Original 22.6 kB
  • After minification 22.6 kB
  • After compression 22.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. Nextcore.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (67%)

Requests Now

57

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nextcore.co

nextcore.co

249 ms

www.nextcore.co

www.nextcore.co

571 ms

css2

css2

61 ms

mbw8ebu.css

mbw8ebu.css

115 ms

breeze_e6fae855021a88a0067fcc58121c594f.css

breeze_e6fae855021a88a0067fcc58121c594f.css

83 ms

breeze_7a4c06f997dfb00f7889b14412d6b1a2.css

breeze_7a4c06f997dfb00f7889b14412d6b1a2.css

155 ms

breeze_6eabd9bac99687194d6a7cb7519dcf28.css

breeze_6eabd9bac99687194d6a7cb7519dcf28.css

283 ms

breeze_d6ff52d31532073aa00bcdb04667d78e.css

breeze_d6ff52d31532073aa00bcdb04667d78e.css

286 ms

breeze_b5e543666f9bc6c8fe095482b233b7b2.css

breeze_b5e543666f9bc6c8fe095482b233b7b2.css

292 ms

breeze_411405fdbf16f009ae655fded0514d0e.css

breeze_411405fdbf16f009ae655fded0514d0e.css

292 ms

slick.css

slick.css

59 ms

breeze_80eef03b50f3de5b6e10e9b100241c8b.js

breeze_80eef03b50f3de5b6e10e9b100241c8b.js

376 ms

breeze_ebd539fc4622ba5b73846bb1c5fccfbb.js

breeze_ebd539fc4622ba5b73846bb1c5fccfbb.js

292 ms

slick.min.js

slick.min.js

66 ms

breeze_ea951177644d47881bd2f765bb80e3eb.js

breeze_ea951177644d47881bd2f765bb80e3eb.js

323 ms

breeze_8f3b3a5586fa83672be3c9fb80b224b9.js

breeze_8f3b3a5586fa83672be3c9fb80b224b9.js

324 ms

breeze_e7334b0f16895605c1234c69ad86fd4a.js

breeze_e7334b0f16895605c1234c69ad86fd4a.js

368 ms

breeze_96738819d2d303105f97a9824735b328.js

breeze_96738819d2d303105f97a9824735b328.js

367 ms

breeze_0d71b35dcc766e31dc965adcdca940a0.js

breeze_0d71b35dcc766e31dc965adcdca940a0.js

368 ms

breeze_49c7a18143e2d74d37f0f3367ff2a35a.js

breeze_49c7a18143e2d74d37f0f3367ff2a35a.js

677 ms

breeze_a1b4a6d452089a2d714e255c0c8aa44f.js

breeze_a1b4a6d452089a2d714e255c0c8aa44f.js

677 ms

breeze_6d6a18b5643b3ca85fe17ad416a6419f.js

breeze_6d6a18b5643b3ca85fe17ad416a6419f.js

678 ms

breeze_86b1e9e44fc0d48859c0ab99c7c6df6e.js

breeze_86b1e9e44fc0d48859c0ab99c7c6df6e.js

677 ms

breeze_48b1f97f9def56ad061a1bd58e55e8f0.js

breeze_48b1f97f9def56ad061a1bd58e55e8f0.js

677 ms

breeze_202c12067f013a56e0f45c53d8220a70.js

breeze_202c12067f013a56e0f45c53d8220a70.js

676 ms

p.css

p.css

31 ms

gtm.js

gtm.js

108 ms

lftracker_v1_lAxoEaKBjv04OYGd.js

lftracker_v1_lAxoEaKBjv04OYGd.js

94 ms

hotjar-1716446.js

hotjar-1716446.js

375 ms

insight.min.js

insight.min.js

510 ms

tr.lfeeder.com

tr.lfeeder.com

770 ms

nextcore-header.png

nextcore-header.png

468 ms

banner-overlay-upper.png

banner-overlay-upper.png

703 ms

banner-overlay-lower.png

banner-overlay-lower.png

966 ms

NextcoreHeader1-1-scaled.jpg

NextcoreHeader1-1-scaled.jpg

1138 ms

solutions-overlay.png

solutions-overlay.png

969 ms

image-icon-square.png

image-icon-square.png

467 ms

image-icon-plus.png

image-icon-plus.png

702 ms

image-icon-trapeze.png

image-icon-trapeze.png

702 ms

card-dot-background.png

card-dot-background.png

965 ms

block-corner.png

block-corner.png

962 ms

NC-icons_NC-lidar-scan.png

NC-icons_NC-lidar-scan.png

962 ms

NC-icons_NC-hardware.png

NC-icons_NC-hardware.png

1129 ms

NC-icons_NC-software.png

NC-icons_NC-software.png

1130 ms

NC-icons_NC-lsolution.png

NC-icons_NC-lsolution.png

1130 ms

footer-statement-background.png

footer-statement-background.png

1140 ms

nextcore-logo-footer.png

nextcore-logo-footer.png

1128 ms

ISO-27001.png

ISO-27001.png

1138 ms

Australian-logo.png

Australian-logo.png

1137 ms

d

d

243 ms

d

d

409 ms

6xKudSxYI9__J9CoKkHzJHQ.ttf

6xKudSxYI9__J9CoKkHzJHQ.ttf

746 ms

6xKjdSxYI9_Hm_-KIms.ttf

6xKjdSxYI9_Hm_-KIms.ttf

911 ms

icons.woff

icons.woff

921 ms

modules.f0cd1ed70b545da08b60.js

modules.f0cd1ed70b545da08b60.js

444 ms

fusion-section-background.jpg

fusion-section-background.jpg

1201 ms

white-dot-corner-overlay.png

white-dot-corner-overlay.png

993 ms

testimonials-background.jpg

testimonials-background.jpg

996 ms

dot-row.png

dot-row.png

993 ms

title-block-corner.png

title-block-corner.png

994 ms

footer-background.jpg

footer-background.jpg

995 ms

d

d

211 ms

d

d

210 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

484 ms

24 ms

67b4d51ea3504defab657835700776c29922e0c09f5643bbaddeff32981b1eb3

67b4d51ea3504defab657835700776c29922e0c09f5643bbaddeff32981b1eb3

97 ms

tr.lfeeder.com

tr.lfeeder.com

34 ms

Accessibility Review

nextcore.co accessibility score

80

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

<frame> or <iframe> elements do not have a title

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

Best Practices

nextcore.co best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

nextcore.co SEO score

86

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nextcore.co 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 Nextcore.co main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

nextcore.co

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