3.1 sec in total
505 ms
2.5 sec
111 ms
Welcome to freecallbutton.com homepage info - get ready to check FREECALLBUTTON best content right away, or after learning these important things about freecallbutton.com
Forsale Lander
Visit freecallbutton.comWe analyzed Freecallbutton.com page load time and found that the first response time was 505 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
freecallbutton.com performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value3.3 s
71/100
25%
Value3.7 s
85/100
10%
Value2,470 ms
4/100
30%
Value0
100/100
15%
Value10.0 s
27/100
10%
505 ms
91 ms
94 ms
95 ms
96 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 36% of them (20 requests) were addressed to the original Freecallbutton.com, 18% (10 requests) were made to Freecallpin.com and 14% (8 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Freecallbutton.com.
Page size can be reduced by 330.8 kB (55%)
599.3 kB
268.5 kB
In fact, the total size of Freecallbutton.com main page is 599.3 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 519.6 kB which makes up the majority of the site volume.
Potential reduce by 18.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 18.4 kB or 79% of the original size.
Potential reduce by 2.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. FREECALLBUTTON images are well optimized though.
Potential reduce by 309.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 309.6 kB or 60% of the original size.
Potential reduce by 511 B
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. Freecallbutton.com needs all CSS files to be minified and compressed as it can save up to 511 B or 59% of the original size.
Number of requests can be reduced by 28 (62%)
45
17
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FREECALLBUTTON. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
freecallbutton.com
505 ms
style.css
91 ms
banjun.js
94 ms
head3.txt
95 ms
head6.txt
96 ms
head7.txt
113 ms
show_ads.js
4 ms
ifr
15 ms
head1.txt
73 ms
head5.txt
75 ms
head8.txt
73 ms
head9.txt
75 ms
head10.txt
74 ms
astrack.js
49 ms
ga.js
6 ms
spacer.gif
50 ms
spacer.bmp
106 ms
logo.png
1384 ms
flag-chinese.gif
406 ms
flag-french.gif
1382 ms
flag-german.gif
1990 ms
flag-italian.gif
106 ms
flag-japanese.gif
108 ms
flag-korean.gif
120 ms
flag-portugese.gif
141 ms
flag-spanish.gif
152 ms
local.png
171 ms
down.png
182 ms
freecallpin1.png
204 ms
spacer.gif
215 ms
worldmap.gif
301 ms
__utm.gif
25 ms
clock.htm
229 ms
ca-pub-3463090114964205.js
23 ms
zrt_lookup.html
27 ms
show_ads_impl.js
35 ms
1888usa.gif
173 ms
ads
251 ms
osd.js
3 ms
ads
305 ms
ads
221 ms
ads
214 ms
timemap.png
35 ms
m_js_controller.js
25 ms
abg.js
35 ms
m_window_focus_non_hydra.js
55 ms
osd_listener.js
54 ms
m_qs_click_protection.js
84 ms
nessie_icon_tiamat_black.png
51 ms
x_button_blue2.png
48 ms
googlelogo_dark_color_84x28dp.png
50 ms
s
30 ms
iconx2-000000.png
26 ms
transparent.png
3 ms
8K3Zg6NpZGSge3qWJUIO0OW0x1SCW4IXoAiImY1mvc4.js
2 ms
activeview
12 ms
freecallbutton.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
freecallbutton.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
Missing source maps for large first-party JavaScript
freecallbutton.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
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 Freecallbutton.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 Freecallbutton.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.
freecallbutton.com
Open Graph description is not detected on the main page of FREECALLBUTTON. 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: