Tools & Wizards About Us
mattinglylab.com screenshot

Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

mattinglylab.com

GLaDOS官网｜中文登录入口、客户端下载与连接指南

Page Load Speed

2.2 sec in total

First Response

679 ms

Resources Loaded

1.4 sec

Page Rendered

197 ms

mattinglylab.com screenshot

About Website

Click here to check amazing Mattinglylab content. Otherwise, check out these important facts you probably never knew about mattinglylab.com

GLaDOS中文登录入口与客户端使用信息整理，涵盖账号登录、安卓及电脑客户端下载、安装配置和连接方法；遇到官网进不去、页面打不开、登录失败或客户端无法连接，可按照域名、网络环境、浏览器与账号状态逐项检查。

Visit mattinglylab.com

Key Findings

We analyzed Mattinglylab.com page load time and found that the first response time was 679 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

mattinglylab.com performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

mattinglylab.com

679 ms

webfont.js

35 ms

wp-emoji-release.min.js

105 ms

style.css

177 ms

media.css

107 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 40% of them (31 requests) were addressed to the original Mattinglylab.com, 45% (35 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (679 ms) belongs to the original domain Mattinglylab.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 904.5 kB (57%)

Content Size

1.6 MB

After Optimization

687.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mattinglylab.com main page is 1.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. 65% of websites need less resources to load. Javascripts take 794.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 87.1 kB

  • Original 116.7 kB
  • After minification 116.1 kB
  • After compression 29.6 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 87.1 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 299.4 kB
  • After minification 299.4 kB

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. Mattinglylab images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 490.0 kB

  • Original 794.6 kB
  • After minification 718.6 kB
  • After compression 304.6 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 490.0 kB or 62% of the original size.

CSS Optimization

-86%

Potential reduce by 327.4 kB

  • Original 381.1 kB
  • After minification 333.0 kB
  • After compression 53.8 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. Mattinglylab.com needs all CSS files to be minified and compressed as it can save up to 327.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (75%)

Requests Now

40

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mattinglylab.com

mattinglylab.com

679 ms

webfont.js

webfont.js

35 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

105 ms

style.css

style.css

177 ms

media.css

media.css

107 ms

animate-custom.css

animate-custom.css

96 ms

layerslider.css

layerslider.css

98 ms

css

css

22 ms

flexslider.css

flexslider.css

89 ms

style.css

style.css

198 ms

jquery.js

jquery.js

200 ms

jquery-migrate.min.js

jquery-migrate.min.js

146 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

206 ms

greensock.js

greensock.js

200 ms

layerslider.transitions.js

layerslider.transitions.js

199 ms

css

css

18 ms

fontawesome.css

fontawesome.css

220 ms

widgets.js

widgets.js

7 ms

js

js

6 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

329 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

331 ms

modernizr-min.js

modernizr-min.js

330 ms

jquery.carouFredSel-6.2.1-min.js

jquery.carouFredSel-6.2.1-min.js

332 ms

jquery.prettyPhoto-min.js

jquery.prettyPhoto-min.js

331 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

332 ms

jquery.fitvids-min.js

jquery.fitvids-min.js

334 ms

gmap-min.js

gmap-min.js

334 ms

main.js

main.js

336 ms

wp-embed.min.js

wp-embed.min.js

334 ms

analytics.js

analytics.js

55 ms

rough_grey_bg.jpg

rough_grey_bg.jpg

198 ms

zebrafish_bg.jpg

zebrafish_bg.jpg

199 ms

mattinglylab_ctd.png

mattinglylab_ctd.png

163 ms

sep-shadow.png

sep-shadow.png

164 ms

CTD_Logo_1-1.jpg

CTD_Logo_1-1.jpg

162 ms

zebrafish_ncsu.jpg

zebrafish_ncsu.jpg

199 ms

mem8YaGs126MiZpBA-UFVZ0df8pkAg.woff

mem8YaGs126MiZpBA-UFVZ0df8pkAg.woff

110 ms

mem8YaGs126MiZpBA-UFW50df8pkAp6a.woff

mem8YaGs126MiZpBA-UFW50df8pkAp6a.woff

113 ms

mem8YaGs126MiZpBA-UFWp0df8pkAp6a.woff

mem8YaGs126MiZpBA-UFWp0df8pkAp6a.woff

116 ms

mem8YaGs126MiZpBA-UFVp0df8pkAp6a.woff

mem8YaGs126MiZpBA-UFVp0df8pkAp6a.woff

115 ms

mem8YaGs126MiZpBA-UFWZ0df8pkAp6a.woff

mem8YaGs126MiZpBA-UFWZ0df8pkAp6a.woff

111 ms

mem8YaGs126MiZpBA-UFUZ0df8pkAp6a.woff

mem8YaGs126MiZpBA-UFUZ0df8pkAp6a.woff

111 ms

mem8YaGs126MiZpBA-UFWJ0df8pkAp6a.woff

mem8YaGs126MiZpBA-UFWJ0df8pkAp6a.woff

116 ms

mem5YaGs126MiZpBA-UN_r8OUuhvKKSTjw.woff

mem5YaGs126MiZpBA-UN_r8OUuhvKKSTjw.woff

118 ms

mem5YaGs126MiZpBA-UN_r8OXOhvKKSTj5PW.woff

mem5YaGs126MiZpBA-UN_r8OXOhvKKSTj5PW.woff

118 ms

mem5YaGs126MiZpBA-UN_r8OXehvKKSTj5PW.woff

mem5YaGs126MiZpBA-UN_r8OXehvKKSTj5PW.woff

118 ms

mem5YaGs126MiZpBA-UN_r8OUehvKKSTj5PW.woff

mem5YaGs126MiZpBA-UN_r8OUehvKKSTj5PW.woff

117 ms

mem5YaGs126MiZpBA-UN_r8OXuhvKKSTj5PW.woff

mem5YaGs126MiZpBA-UN_r8OXuhvKKSTj5PW.woff

114 ms

mem5YaGs126MiZpBA-UN_r8OVuhvKKSTj5PW.woff

mem5YaGs126MiZpBA-UN_r8OVuhvKKSTj5PW.woff

118 ms

mem5YaGs126MiZpBA-UN_r8OX-hvKKSTj5PW.woff

mem5YaGs126MiZpBA-UN_r8OX-hvKKSTj5PW.woff

118 ms

mem5YaGs126MiZpBA-UN7rgOUuhvKKSTjw.woff

mem5YaGs126MiZpBA-UN7rgOUuhvKKSTjw.woff

121 ms

mem5YaGs126MiZpBA-UN7rgOXOhvKKSTj5PW.woff

mem5YaGs126MiZpBA-UN7rgOXOhvKKSTj5PW.woff

122 ms

mem5YaGs126MiZpBA-UN7rgOXehvKKSTj5PW.woff

mem5YaGs126MiZpBA-UN7rgOXehvKKSTj5PW.woff

120 ms

mem5YaGs126MiZpBA-UN7rgOUehvKKSTj5PW.woff

mem5YaGs126MiZpBA-UN7rgOUehvKKSTj5PW.woff

118 ms

mem5YaGs126MiZpBA-UN7rgOXuhvKKSTj5PW.woff

mem5YaGs126MiZpBA-UN7rgOXuhvKKSTj5PW.woff

122 ms

mem5YaGs126MiZpBA-UN7rgOVuhvKKSTj5PW.woff

mem5YaGs126MiZpBA-UN7rgOVuhvKKSTj5PW.woff

122 ms

mem5YaGs126MiZpBA-UN7rgOX-hvKKSTj5PW.woff

mem5YaGs126MiZpBA-UN7rgOX-hvKKSTj5PW.woff

122 ms

mem6YaGs126MiZpBA-UFUK0ZdctGAK6b.woff

mem6YaGs126MiZpBA-UFUK0ZdctGAK6b.woff

125 ms

mem6YaGs126MiZpBA-UFUK0XdctGAK6bt6o.woff

mem6YaGs126MiZpBA-UFUK0XdctGAK6bt6o.woff

124 ms

mem6YaGs126MiZpBA-UFUK0WdctGAK6bt6o.woff

mem6YaGs126MiZpBA-UFUK0WdctGAK6bt6o.woff

125 ms

mem6YaGs126MiZpBA-UFUK0adctGAK6bt6o.woff

mem6YaGs126MiZpBA-UFUK0adctGAK6bt6o.woff

124 ms

mem6YaGs126MiZpBA-UFUK0VdctGAK6bt6o.woff

mem6YaGs126MiZpBA-UFUK0VdctGAK6bt6o.woff

126 ms

mem6YaGs126MiZpBA-UFUK0ddctGAK6bt6o.woff

mem6YaGs126MiZpBA-UFUK0ddctGAK6bt6o.woff

127 ms

mem6YaGs126MiZpBA-UFUK0UdctGAK6bt6o.woff

mem6YaGs126MiZpBA-UFUK0UdctGAK6bt6o.woff

127 ms

memnYaGs126MiZpBA-UFUKWiUNhrIqWxjaPX.woff

memnYaGs126MiZpBA-UFUKWiUNhrIqWxjaPX.woff

128 ms

memnYaGs126MiZpBA-UFUKWiUNhlIqWxjaPXZSk.woff

memnYaGs126MiZpBA-UFUKWiUNhlIqWxjaPXZSk.woff

128 ms

memnYaGs126MiZpBA-UFUKWiUNhkIqWxjaPXZSk.woff

memnYaGs126MiZpBA-UFUKWiUNhkIqWxjaPXZSk.woff

129 ms

memnYaGs126MiZpBA-UFUKWiUNhoIqWxjaPXZSk.woff

memnYaGs126MiZpBA-UFUKWiUNhoIqWxjaPXZSk.woff

129 ms

memnYaGs126MiZpBA-UFUKWiUNhnIqWxjaPXZSk.woff

memnYaGs126MiZpBA-UFUKWiUNhnIqWxjaPXZSk.woff

130 ms

memnYaGs126MiZpBA-UFUKWiUNhvIqWxjaPXZSk.woff

memnYaGs126MiZpBA-UFUKWiUNhvIqWxjaPXZSk.woff

131 ms

memnYaGs126MiZpBA-UFUKWiUNhmIqWxjaPXZSk.woff

memnYaGs126MiZpBA-UFUKWiUNhmIqWxjaPXZSk.woff

131 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

134 ms

collect

collect

90 ms

common.js

common.js

51 ms

util.js

util.js

52 ms

geocoder.js

geocoder.js

51 ms

widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html

widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html

39 ms

Accessibility Review

mattinglylab.com accessibility score

93

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

Document doesn't have a <title> element

Best Practices

mattinglylab.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

SEO Factors

mattinglylab.com SEO score

77

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mattinglylab.com 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 Mattinglylab.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

mattinglylab.com

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