Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

aggregate.digital

Internet of Things Platform, Remote Monitoring and Service, M2M, IoT

Page Load Speed

7 sec in total

First Response

239 ms

Resources Loaded

5.3 sec

Page Rendered

1.4 sec

aggregate.digital screenshot

About Website

Click here to check amazing Aggregate content. Otherwise, check out these important facts you probably never knew about aggregate.digital

AggreGate is a white-label Internet of Things low-code platform that employs modern network technologies to control, configure and monitor different electronic devices.

Visit aggregate.digital

Key Findings

We analyzed Aggregate.digital page load time and found that the first response time was 239 ms and then it took 6.7 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

aggregate.digital performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value44.4 s

0/100

25%

SI (Speed Index)

Value26.3 s

0/100

10%

TBT (Total Blocking Time)

Value48,120 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value76.3 s

0/100

10%

Network Requests Diagram

aggregate.digital

239 ms

aggregate.digital

848 ms

pixel.php

310 ms

js

72 ms

script_1641973979.js

305 ms

Our browser made a total of 172 requests to load all elements on the main page. We found that 81% of them (140 requests) were addressed to the original Aggregate.digital, 5% (8 requests) were made to Mc.yandex.com and 3% (6 requests) were made to Yastatic.net. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Mc.yandex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 918.0 kB (20%)

Content Size

4.6 MB

After Optimization

3.7 MB

In fact, the total size of Aggregate.digital main page is 4.6 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. Only a small number of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 117.0 kB

  • Original 138.7 kB
  • After minification 116.8 kB
  • After compression 21.7 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 21.9 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 117.0 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 150.5 kB

  • Original 3.4 MB
  • After minification 3.2 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. Aggregate images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 16.2 kB

  • Original 301.7 kB
  • After minification 299.0 kB
  • After compression 285.5 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

-84%

Potential reduce by 634.2 kB

  • Original 755.9 kB
  • After minification 746.7 kB
  • After compression 121.7 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. Aggregate.digital needs all CSS files to be minified and compressed as it can save up to 634.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (37%)

Requests Now

145

After Optimization

92

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

Accessibility Review

aggregate.digital accessibility score

51

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

aggregate.digital best practices score

50

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

aggregate.digital SEO score

76

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

Links are not crawlable

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 Aggregate.digital 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 Aggregate.digital 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 description is not detected on the main page of Aggregate. 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: