2.3 sec in total
262 ms
1.9 sec
165 ms
Click here to check amazing MER content for United States. Otherwise, check out these important facts you probably never knew about mer.com
Visit mer.comWe analyzed Mer.com page load time and found that the first response time was 262 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 40% of websites can load faster.
mer.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value11.5 s
0/100
25%
Value7.0 s
32/100
10%
Value2,600 ms
4/100
30%
Value0.032
100/100
15%
Value14.8 s
8/100
10%
262 ms
789 ms
75 ms
129 ms
210 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Mer.com, 79% (34 requests) were made to Mer.org and 5% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (789 ms) relates to the external source Mer.org.
Page size can be reduced by 331.2 kB (52%)
635.9 kB
304.7 kB
In fact, the total size of Mer.com main page is 635.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 304.7 kB which makes up the majority of the site volume.
Potential reduce by 26 B
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 26 B or 19% of the original size.
Potential reduce by 67.8 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. Obviously, MER needs image optimization as it can save up to 67.8 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 211.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 211.6 kB or 69% of the original size.
Potential reduce by 51.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. Mer.com needs all CSS files to be minified and compressed as it can save up to 51.7 kB or 85% of the original size.
Number of requests can be reduced by 5 (13%)
40
35
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MER. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
mer.com
262 ms
mer.org
789 ms
main.css
75 ms
jquery-ui-1.7.2.custom.css
129 ms
jquery-1.4.2.min.js
210 ms
jquery-ui-1.8.2.custom.min.js
265 ms
main.js
140 ms
AC_RunActiveContent.js
148 ms
conversion.js
14 ms
side_bkg.png
73 ms
header_bkg_green.png
73 ms
Left-header-logo.png
192 ms
refer-a-colleague.png
83 ms
refer-a-colleague_blank.png
74 ms
register-now_new.png
72 ms
girl.png
261 ms
navbar_bkg_new.png
136 ms
headline.png
142 ms
icon_facebook_40.png
142 ms
icon_youtube_40.png
150 ms
icon_twitter_40.png
201 ms
icon_linkedin_40.png
207 ms
primary_care_physician.png
402 ms
gray_arrow.png
214 ms
loading24.gif
262 ms
blend1.jpg
241 ms
blend2.jpg
246 ms
bkg_fade.png
255 ms
ga.js
5 ms
32 ms
__utm.gif
16 ms
sw.js
34 ms
32 ms
cq_blank.gif
7 ms
32 ms
header_button1_over.jpg
74 ms
header_button2_over.jpg
67 ms
header2_04_over.jpg
82 ms
menu_10_over.jpg
72 ms
menu_11_over.jpg
73 ms
menu_12_over.jpg
74 ms
menu_13_over.jpg
133 ms
menu_14_over.jpg
152 ms
mer.com 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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
mer.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
mer.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mer.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mer.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
mer.com
Open Graph description is not detected on the main page of MER. 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: