Access thinga.me. Microsoft Research Lab - Cambridge

Report Summary

About Website

Welcome to thinga.me homepage info - get ready to check Thinga best content for United States right away, or after learning these important things about thinga.me

At Microsoft Research in Cambridge, we aspire to transform the world through deep research in areas of AI, confidential computing, healthcare, and more.

Visit thinga.me

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

1153 ms

style.min.css

22 ms

shortcodes.css

38 ms

shared-style.css

40 ms

style.css

37 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Thinga.me, 14% (9 requests) were made to C.s-microsoft.com and 2% (1 request) were made to Wcpstatic.microsoft.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Microsoft.com.

Content Size

3.1 MB

After Optimization

2.4 MB

In fact, the total size of Thinga.me 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. 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.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 172.7 kB

Original 203.7 kB
After minification 188.2 kB
After compression 31.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 172.7 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 61.9 kB

Original 2.1 MB
After minification 2.0 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. Thinga images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 261.4 kB

Original 447.5 kB
After minification 445.1 kB
After compression 186.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 261.4 kB or 58% of the original size.

CSS Optimization

-60%

Potential reduce by 250.1 kB

Original 418.0 kB
After minification 415.0 kB
After compression 167.9 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. Thinga.me needs all CSS files to be minified and compressed as it can save up to 250.1 kB or 60% of the original size.

Requests Now

After Optimization

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thinga. 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 20 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links are not crawlable

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

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 Thinga.me 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 Thinga.me 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

thinga.me

Open Graph data is detected on the main page of Thinga. 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

Microsoft Research Lab - Cambridge - Microsoft Research

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)