Tools & Wizards About Us
grimes.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

grimes.com

Telepathy - Powering Successful Brands

Page Load Speed

1.9 sec in total

First Response

51 ms

Resources Loaded

1.1 sec

Page Rendered

682 ms

grimes.com screenshot

About Website

Visit grimes.com now to see the best up-to-date Grimes content and also check out these interesting facts you probably never knew about grimes.com

Visit grimes.com

Key Findings

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

Performance Metrics

grimes.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,100 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value9.3 s

32/100

10%

Network Requests Diagram

www.telepathy.com

51 ms

www.telepathy.com

107 ms

telepathy.com

48 ms

telepathy.com

262 ms

A.style.css,qver=1.1.pagespeed.cf.YqjtyaNdND.css

78 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Grimes.com, 10% (4 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (262 ms) relates to the external source Telepathy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 298.2 kB (28%)

Content Size

1.1 MB

After Optimization

784.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Grimes.com main page is 1.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. 40% of websites need less resources to load. HTML takes 597.8 kB which makes up the majority of the site volume.

HTML Optimization

-50%

Potential reduce by 297.8 kB

  • Original 597.8 kB
  • After minification 584.2 kB
  • After compression 300.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 297.8 kB or 50% of the original size.

Image Optimization

-0%

Potential reduce by 38 B

  • Original 387.3 kB
  • After minification 387.3 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. Grimes images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 362 B

  • Original 90.6 kB
  • After minification 90.6 kB
  • After compression 90.3 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 31 B

  • Original 6.7 kB
  • After minification 6.7 kB
  • After compression 6.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. Grimes.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (34%)

Requests Now

32

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.telepathy.com

www.telepathy.com

51 ms

www.telepathy.com

www.telepathy.com

107 ms

telepathy.com

telepathy.com

48 ms

telepathy.com

telepathy.com

262 ms

A.style.css,qver=1.1.pagespeed.cf.YqjtyaNdND.css

A.style.css,qver=1.1.pagespeed.cf.YqjtyaNdND.css

78 ms

js

js

61 ms

css

css

30 ms

jquery.min.js

jquery.min.js

40 ms

jquery.form.js+jquery.queryloader2.js+modernizr-2.6.2.min.js.pagespeed.jc.ty3ZmKqA1U.js

jquery.form.js+jquery.queryloader2.js+modernizr-2.6.2.min.js.pagespeed.jc.ty3ZmKqA1U.js

39 ms

jquery.fitvids.js

jquery.fitvids.js

39 ms

jquery.appear.js+jquery.slabtext.min.js+jquery.fittext.js+jquery.easing.min.js+jquery.parallax-1.1.3.js+jquery.prettyPhoto.js+jquery.sticky.js+selectnav.min.js+SmoothScroll.js+jquery.flexslider-min.js+isotope.js.pagespeed.jc.YBcvazBd8m.js

jquery.appear.js+jquery.slabtext.min.js+jquery.fittext.js+jquery.easing.min.js+jquery.parallax-1.1.3.js+jquery.prettyPhoto.js+jquery.sticky.js+selectnav.min.js+SmoothScroll.js+jquery.flexslider-min.js+isotope.js.pagespeed.jc.YBcvazBd8m.js

63 ms

bootstrap-modal.js+shortcodes.js+scripts.js+jquery.svg3dtagcloud.min.js,qver==1.0.pagespeed.jc.FMoW6r-h1x.js

bootstrap-modal.js+shortcodes.js+scripts.js+jquery.svg3dtagcloud.min.js,qver==1.0.pagespeed.jc.FMoW6r-h1x.js

61 ms

carbon-sm.jpg

carbon-sm.jpg

200 ms

xtelepathy-logo-large.png.pagespeed.ic.sZzDzOVa8h.png

xtelepathy-logo-large.png.pagespeed.ic.sZzDzOVa8h.png

200 ms

xtelepathy-logo.png.pagespeed.ic.uW0aun8o4p.png

xtelepathy-logo.png.pagespeed.ic.uW0aun8o4p.png

200 ms

xlaunch-sm.jpg.pagespeed.ic.vOJAMyTdQW.jpg

xlaunch-sm.jpg.pagespeed.ic.vOJAMyTdQW.jpg

201 ms

xpattern.png.pagespeed.ic.uNoTDSyrgw.png

xpattern.png.pagespeed.ic.uNoTDSyrgw.png

200 ms

xupward.png.pagespeed.ic.8geatSJzhF.png

xupward.png.pagespeed.ic.8geatSJzhF.png

251 ms

xcraftwork.com.png.pagespeed.ic.RRD1yeBApa.png

xcraftwork.com.png.pagespeed.ic.RRD1yeBApa.png

205 ms

xcolossal.com.png.pagespeed.ic.xSO9VWXPE2.png

xcolossal.com.png.pagespeed.ic.xSO9VWXPE2.png

203 ms

xsmoothly.png.pagespeed.ic.HZAVQF2gRO.png

xsmoothly.png.pagespeed.ic.HZAVQF2gRO.png

251 ms

xcohere.jpg.pagespeed.ic.mfMBaMxIKO.jpg

xcohere.jpg.pagespeed.ic.mfMBaMxIKO.jpg

202 ms

xparallax3.jpg.pagespeed.ic.Xar52Lix5G.jpg

xparallax3.jpg.pagespeed.ic.Xar52Lix5G.jpg

204 ms

xtelepathy-logo2.png.pagespeed.ic.VscLAd6J4_.png

xtelepathy-logo2.png.pagespeed.ic.VscLAd6J4_.png

252 ms

xica-badge.jfif.pagespeed.ic.JQE7Ftlt0x.jpg

xica-badge.jfif.pagespeed.ic.JQE7Ftlt0x.jpg

252 ms

ga.js

ga.js

130 ms

xbacktotop.png.pagespeed.ic.HwB9tUjgK6.png

xbacktotop.png.pagespeed.ic.HwB9tUjgK6.png

179 ms

BebasNeue-webfont.woff

BebasNeue-webfont.woff

178 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

79 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

112 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

112 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

124 ms

__utm.gif

__utm.gif

25 ms

xupward.png.pagespeed.ic.8geatSJzhF.png

xupward.png.pagespeed.ic.8geatSJzhF.png

26 ms

xcraftwork.com.png.pagespeed.ic.RRD1yeBApa.png

xcraftwork.com.png.pagespeed.ic.RRD1yeBApa.png

27 ms

xcolossal.com.png.pagespeed.ic.xSO9VWXPE2.png

xcolossal.com.png.pagespeed.ic.xSO9VWXPE2.png

25 ms

xsmoothly.png.pagespeed.ic.HZAVQF2gRO.png

xsmoothly.png.pagespeed.ic.HZAVQF2gRO.png

70 ms

xcohere.jpg.pagespeed.ic.mfMBaMxIKO.jpg

xcohere.jpg.pagespeed.ic.mfMBaMxIKO.jpg

24 ms

xarrow_left.png.pagespeed.ic.wNJkMLODEb.png

xarrow_left.png.pagespeed.ic.wNJkMLODEb.png

25 ms

xarrow_right.png.pagespeed.ic.Vd5mhf4bji.png

xarrow_right.png.pagespeed.ic.Vd5mhf4bji.png

47 ms

xselectmenu-light.png.pagespeed.ic.-Gzx43NFmC.png

xselectmenu-light.png.pagespeed.ic.-Gzx43NFmC.png

47 ms

Accessibility Review

grimes.com accessibility score

75

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.

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

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

grimes.com best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

grimes.com SEO score

79

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

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

grimes.com

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