Tools & Wizards About Us
likeme.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

likeme.com

Nautilus Ventures

Page Load Speed

2.4 sec in total

First Response

256 ms

Resources Loaded

1.4 sec

Page Rendered

731 ms

likeme.com screenshot

About Website

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

Angel investors.

Visit likeme.com

Key Findings

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

Performance Metrics

likeme.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.6 s

0/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value910 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.177

68/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

likeme.com

256 ms

webfont.js

18 ms

128 ms

128 ms

style.css

122 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Likeme.com, 22% (12 requests) were made to S2.wp.com and 15% (8 requests) were made to Explorersdotcom.files.wordpress.com. The less responsive or slowest element that took the longest time to load (336 ms) relates to the external source Use.typekit.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 436.0 kB (26%)

Content Size

1.7 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Likeme.com main page is 1.7 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 50.4 kB

  • Original 65.8 kB
  • After minification 64.3 kB
  • After compression 15.4 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 50.4 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 976 B

  • Original 1.1 MB
  • After minification 1.1 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. Likeme images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 352.6 kB

  • Original 474.8 kB
  • After minification 364.5 kB
  • After compression 122.2 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 352.6 kB or 74% of the original size.

CSS Optimization

-76%

Potential reduce by 32.0 kB

  • Original 41.9 kB
  • After minification 39.4 kB
  • After compression 9.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. Likeme.com needs all CSS files to be minified and compressed as it can save up to 32.0 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (54%)

Requests Now

41

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

likeme.com

likeme.com

256 ms

webfont.js

webfont.js

18 ms

128 ms

128 ms

style.css

style.css

122 ms

s1.wp.com

s1.wp.com

116 ms

gprofiles.js

gprofiles.js

177 ms

wpgroho.js

wpgroho.js

119 ms

119 ms

jetpack-carousel.css

jetpack-carousel.css

116 ms

tiled-gallery.css

tiled-gallery.css

119 ms

126 ms

widgets.js

widgets.js

100 ms

118 ms

w.js

w.js

98 ms

xue0vwj.js

xue0vwj.js

336 ms

merriweather.css

merriweather.css

6 ms

41475_719240190_4474_n.jpg

41475_719240190_4474_n.jpg

157 ms

icon-comments-2x.png

icon-comments-2x.png

153 ms

10041372546_2cd2f8cb51.jpg

10041372546_2cd2f8cb51.jpg

164 ms

9961509506_7311ed0466.jpg

9961509506_7311ed0466.jpg

334 ms

9766434174_3bf30fb205.jpg

9766434174_3bf30fb205.jpg

164 ms

9576442325_c15fb80ec9.jpg

9576442325_c15fb80ec9.jpg

319 ms

9553696310_423275a7fc.jpg

9553696310_423275a7fc.jpg

181 ms

9986306666_d5691409ac_b.jpg

9986306666_d5691409ac_b.jpg

137 ms

20131201_gould_bay_emperor_12w51.jpg

20131201_gould_bay_emperor_12w51.jpg

138 ms

thecoffeeshop-x3.jpg

thecoffeeshop-x3.jpg

139 ms

icon-rss-2x.png

icon-rss-2x.png

139 ms

icon-twitter-2x.png

icon-twitter-2x.png

140 ms

icon-google-2x.png

icon-google-2x.png

141 ms

icon-flickr-2x.png

icon-flickr-2x.png

140 ms

08557ef217c6fdadb8015328bc3e8fd3

08557ef217c6fdadb8015328bc3e8fd3

141 ms

f9e758d31f2c1343e606f0160c749a41

f9e758d31f2c1343e606f0160c749a41

142 ms

select_arrow.gif

select_arrow.gif

64 ms

Noticons.svg

Noticons.svg

67 ms

BaABdRAi2AAAA

BaABdRAi2AAAA

63 ms

merriweather-bold-webfont.ttf

merriweather-bold-webfont.ttf

94 ms

merriweather-regular-webfont.ttf

merriweather-regular-webfont.ttf

92 ms

merriweather-light-webfont.ttf

merriweather-light-webfont.ttf

155 ms

hovercard.css

hovercard.css

120 ms

services.css

services.css

119 ms

41475_719240190_4474_n.jpg

41475_719240190_4474_n.jpg

186 ms

9986306666_d5691409ac_b.jpg

9986306666_d5691409ac_b.jpg

186 ms

20131201_gould_bay_emperor_12w51.jpg

20131201_gould_bay_emperor_12w51.jpg

187 ms

thecoffeeshop-x3.jpg

thecoffeeshop-x3.jpg

186 ms

g.gif

g.gif

93 ms

g.gif

g.gif

67 ms

g.gif

g.gif

67 ms

likeme.com

likeme.com

270 ms

MZmRPWlgBhM8ud-gTLhWB-gJoyuzcKJH00d_VxWdIVSff4RqgsMdeMJ6Mk6f5Mb.woff

MZmRPWlgBhM8ud-gTLhWB-gJoyuzcKJH00d_VxWdIVSff4RqgsMdeMJ6Mk6f5Mb.woff

38 ms

3_Qvu6lG78P1rUWPifKKBltYe5Py3dHja0skBF7yjXjff5VKMUMdeMJ6Mk6f5Mt.woff

3_Qvu6lG78P1rUWPifKKBltYe5Py3dHja0skBF7yjXjff5VKMUMdeMJ6Mk6f5Mt.woff

102 ms

flJlVytFPTxlzf4DsHHZqhLAWlmvW798idK-t6BxKaSff5LKMUMdeMJ6Mk6f5gI.woff

flJlVytFPTxlzf4DsHHZqhLAWlmvW798idK-t6BxKaSff5LKMUMdeMJ6Mk6f5gI.woff

142 ms

O5FGAMBCVN_hDtG1XVoqRS_Zfq4_-NvMrKhP_Gf_fobff5OKMUMdeMJ6Mk6f5Mb.woff

O5FGAMBCVN_hDtG1XVoqRS_Zfq4_-NvMrKhP_Gf_fobff5OKMUMdeMJ6Mk6f5Mb.woff

156 ms

ApgNsC9FMQ1y8FBT9usEX0czSSkEIX1lZ4sjrYnh8wvff5dKMUMdeMJ6Mk6f5MS.woff

ApgNsC9FMQ1y8FBT9usEX0czSSkEIX1lZ4sjrYnh8wvff5dKMUMdeMJ6Mk6f5MS.woff

289 ms

p.gif

p.gif

158 ms

Accessibility Review

likeme.com accessibility score

76

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

likeme.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Likeme.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Likeme.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

likeme.com

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