Tools & Wizards About Us
thinkin.io screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

thinkin.io

Indoor location and position tracking | ThinkIN®

Page Load Speed

10.3 sec in total

First Response

690 ms

Resources Loaded

8.8 sec

Page Rendered

888 ms

thinkin.io screenshot

About Website

Click here to check amazing ThinkIN content. Otherwise, check out these important facts you probably never knew about thinkin.io

Scopri il valore della location intelligence e i vantaggi del conoscere in tempo reale la posizione di risorse e persone all'interno di uno spazio indoor.

Visit thinkin.io

Key Findings

We analyzed Thinkin.io page load time and found that the first response time was 690 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

thinkin.io performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value1,620 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

thinkin.io

690 ms

gtm.js

80 ms

css2

42 ms

jquery.js

64 ms

jquery.easing.js

76 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 64% of them (42 requests) were addressed to the original Thinkin.io, 14% (9 requests) were made to Fonts.gstatic.com and 11% (7 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (7.7 sec) belongs to the original domain Thinkin.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 412.2 kB (13%)

Content Size

3.1 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thinkin.io main page is 3.1 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. 60% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 113.8 kB

  • Original 137.8 kB
  • After minification 123.4 kB
  • After compression 24.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 113.8 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 271.9 kB

  • Original 2.6 MB
  • After minification 2.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. ThinkIN images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 26.5 kB

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

CSS Optimization

-0%

Potential reduce by 45 B

  • Original 25.2 kB
  • After minification 25.2 kB
  • After compression 25.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. Thinkin.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (27%)

Requests Now

56

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thinkin.io

thinkin.io

690 ms

gtm.js

gtm.js

80 ms

css2

css2

42 ms

jquery.js

jquery.js

64 ms

jquery.easing.js

jquery.easing.js

76 ms

jquery.validate.js

jquery.validate.js

84 ms

jquery.validate.unobtrusive.js

jquery.validate.unobtrusive.js

81 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

96 ms

bootstrap.min.css

bootstrap.min.css

90 ms

tiny-slider.css

tiny-slider.css

96 ms

main-css.css.v638627149837035055

main-css.css.v638627149837035055

231 ms

main-js.js.v638627149837035055

main-js.js.v638627149837035055

572 ms

stub.js

stub.js

39 ms

iubenda_cs.js

iubenda_cs.js

42 ms

gsap.min.js

gsap.min.js

46 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

57 ms

api.js

api.js

35 ms

icona-menu-tecnologie.png

icona-menu-tecnologie.png

298 ms

icona-menu-soluzioni.png

icona-menu-soluzioni.png

313 ms

copia-di-testata-sito-x-ita-3.gif

copia-di-testata-sito-x-ita-3.gif

7665 ms

testata-industry-mobile.png

testata-industry-mobile.png

474 ms

copia-di-testata-sito-x-ita-2.gif

copia-di-testata-sito-x-ita-2.gif

5870 ms

testata-retails-mobile.png

testata-retails-mobile.png

844 ms

testata-healthcare-ottimizzata.webp

testata-healthcare-ottimizzata.webp

747 ms

estata-healthcare-mobile-ottimizzata.webp

estata-healthcare-mobile-ottimizzata.webp

748 ms

2.png

2.png

639 ms

1.png

1.png

874 ms

5.png

5.png

1115 ms

9.png

9.png

1011 ms

6.png

6.png

1608 ms

3.png

3.png

1115 ms

4.png

4.png

1260 ms

8.png

8.png

1252 ms

7.png

7.png

1236 ms

10.png

10.png

1378 ms

la-soluzione-thinkin-in-1-min.png

la-soluzione-thinkin-in-1-min.png

3074 ms

tavola-1-thinkin_tavola-webp_disegno-1.webp

tavola-1-thinkin_tavola-webp_disegno-1.webp

1432 ms

tavola-2-thinkin_tavola-disegno-1.png

tavola-2-thinkin_tavola-disegno-1.png

1513 ms

tavola-3-thinkin_tavola-disegno-1.png

tavola-3-thinkin_tavola-disegno-1.png

1585 ms

tavola-4-thinkin_tavola-disegno-1.png

tavola-4-thinkin_tavola-disegno-1.png

1750 ms

dettaglio-industry.webp

dettaglio-industry.webp

1746 ms

tavola-1-thinkin_tavola-disegno-1.webp

tavola-1-thinkin_tavola-disegno-1.webp

1743 ms

dettaglio-healthcare.webp

dettaglio-healthcare.webp

1864 ms

icona-1.webp

icona-1.webp

1875 ms

icona-2.webp

icona-2.webp

1870 ms

icona-3.png

icona-3.png

1994 ms

demo_def.webp

demo_def.webp

1999 ms

asset-tracking-in-manufacturing.png

asset-tracking-in-manufacturing.png

2200 ms

shutterstock_2025webp_14299.webp

shutterstock_2025webp_14299.webp

2201 ms

various-different-euros-background.jpg

various-different-euros-background.jpg

2204 ms

webp_23_freepik_973.webp

webp_23_freepik_973.webp

2408 ms

recaptcha__en.js

recaptcha__en.js

127 ms

2c1.jpg

2c1.jpg

2375 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

35 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

76 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

198 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

213 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

213 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

211 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

213 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

213 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

212 ms

175.jpg

175.jpg

2101 ms

donna-di-vista-laterale-che-lavora-al-computer-portatile.jpg

donna-di-vista-laterale-che-lavora-al-computer-portatile.jpg

2234 ms

technology_1717.jpg

technology_1717.jpg

2181 ms

h-chart-stock-market-graphic-webp_diagram.webp

h-chart-stock-market-graphic-webp_diagram.webp

2118 ms

Accessibility Review

thinkin.io accessibility score

61

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA progressbar elements do not have accessible names.

High

ARIA IDs are not unique

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

Low

No form fields have multiple labels

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

thinkin.io best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

thinkin.io SEO score

92

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

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

    IT

  • Language Claimed

    IT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thinkin.io can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it matches the claimed language. Our system also found out that Thinkin.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

thinkin.io

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