3.5 sec in total
86 ms
3.1 sec
377 ms
Visit meer.li now to see the best up-to-date Meer content for United States and also check out these interesting facts you probably never knew about meer.li
Where exceptional mobile designers connect, show off their designs and promote themselves.
Visit meer.liWe analyzed Meer.li page load time and found that the first response time was 86 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
meer.li performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value3.7 s
59/100
25%
Value3.8 s
83/100
10%
Value90 ms
99/100
30%
Value0.112
86/100
15%
Value3.7 s
90/100
10%
86 ms
774 ms
205 ms
4 ms
548 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Meer.li, 28% (16 requests) were made to A0.twimg.com and 19% (11 requests) were made to Iphone.meer.li. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Meerli.s3.amazonaws.com.
Page size can be reduced by 1.1 MB (47%)
2.3 MB
1.2 MB
In fact, the total size of Meer.li main page is 2.3 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 75.2 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 75.2 kB or 78% of the original size.
Potential reduce by 61.2 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. Meer images are well optimized though.
Potential reduce by 321.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 321.2 kB or 67% of the original size.
Potential reduce by 642.1 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. Meer.li needs all CSS files to be minified and compressed as it can save up to 642.1 kB or 95% of the original size.
Number of requests can be reduced by 8 (25%)
32
24
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Meer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
www.meer.li
86 ms
iphone.meer.li
774 ms
application-6579263fe000454e873f60e8ab3d4395.css
205 ms
widgets.js
4 ms
all.js
548 ms
pinit.js
59 ms
application-37944f6378d5f7ace21859ecfba69a6e.js
329 ms
mixpanel-2.1.min.js
102 ms
image_normal.jpg
91 ms
normal_Photo_2013-02-05_01.55.51_PM.png
194 ms
img154edited3_normal.jpg
52 ms
bg.png
52 ms
top_bg.png
62 ms
normal_16_timeline_Wally_cropped.jpg
190 ms
normal_0.png
1680 ms
normal_en1.png
207 ms
normal_App.Store.Screen.Shots.1.1.jpg
207 ms
normal_SplashscreenB.png
451 ms
normal_pinme.png
450 ms
normal_vy1.jpg
244 ms
normal_splash.jpg
245 ms
Photo_on_2010-08-08_at_00.37_normal.jpg
52 ms
image_normal.jpg
51 ms
Berger.Fohr.May.2012_normal.jpg
51 ms
da1qunug703kazcre4o3_normal.png
50 ms
a6gmekhi9mjvq466zk28_normal.png
52 ms
per_normal.jpg
52 ms
ACOtri_normal.jpg
53 ms
avenir_roman.woff
67 ms
avenir_light.woff
67 ms
akzidenzgrotesk_regular.woff
67 ms
akzidenzgrotesk_light.woff
75 ms
icomoon.svg
66 ms
akzidenzgrotesk_italic.woff
66 ms
45 ms
316 ms
image_normal.jpg
143 ms
img154edited3_normal.jpg
140 ms
Photo_on_2010-08-08_at_00.37_normal.jpg
136 ms
image_normal.jpg
137 ms
Berger.Fohr.May.2012_normal.jpg
137 ms
da1qunug703kazcre4o3_normal.png
138 ms
a6gmekhi9mjvq466zk28_normal.png
139 ms
per_normal.jpg
140 ms
ACOtri_normal.jpg
140 ms
xd_arbiter.php
289 ms
xd_arbiter.php
498 ms
ga.js
132 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
138 ms
ping
288 ms
pinit_main.js
98 ms
__utm.gif
16 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
18 ms
jot
91 ms
like.php
196 ms
qeKvIRsJabD.js
516 ms
LVx-xkvaJ0b.png
576 ms
meer.li accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
meer.li best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
meer.li SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Meer.li 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Meer.li 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.
meer.li
Open Graph data is detected on the main page of Meer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: