2.9 sec in total
335 ms
2.4 sec
159 ms
Welcome to 123-sms.net homepage info - get ready to check 123 SMS best content for France right away, or after learning these important things about 123-sms.net
Solution professionnelle qui vous permet d'envoyer des SMS par le web. Alerte sms, mailing-sms, fid?lisation, envois de sms en nombre, sms marketing, api sms.
Visit 123-sms.netWe analyzed 123-sms.net page load time and found that the first response time was 335 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.
123-sms.net performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value5.1 s
25/100
25%
Value9.8 s
10/100
10%
Value1,660 ms
11/100
30%
Value0.403
25/100
15%
Value14.5 s
9/100
10%
335 ms
504 ms
40 ms
101 ms
167 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 84% of them (69 requests) were addressed to the original 123-sms.net, 5% (4 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (647 ms) belongs to the original domain 123-sms.net.
Page size can be reduced by 114.8 kB (11%)
1.1 MB
968.0 kB
In fact, the total size of 123-sms.net 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. 45% of websites need less resources to load. Images take 591.5 kB which makes up the majority of the site volume.
Potential reduce by 51.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. This page needs HTML code to be minified as it can gain 12.7 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 51.0 kB or 81% of the original size.
Potential reduce by 32.5 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. 123 SMS images are well optimized though.
Potential reduce by 27.1 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.
Potential reduce by 4.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. 123-sms.net has all CSS files already compressed.
Number of requests can be reduced by 35 (48%)
73
38
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 123 SMS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
123-sms.net
335 ms
www.123-sms.net
504 ms
api.js
40 ms
tarteaucitron.js
101 ms
bootstrap.css
167 ms
bootstrap-responsive.css
239 ms
style.css
248 ms
icons.css
246 ms
icons-color.css
249 ms
css
46 ms
allinone_bannerWithPlaylist.css
316 ms
jquery.min.js
411 ms
jquery-ui.min.js
25 ms
jquery.ui.touch-punch.min.js
327 ms
jquery.mousewheel.min.js
328 ms
allinone_bannerWithPlaylist.js
395 ms
jqIsoText.min.js
407 ms
validationEngine.jquery.css
432 ms
jquery.validationEngine-en.js
475 ms
jquery.validationEngine.js
571 ms
bootstrap.js
492 ms
flexslider.js
513 ms
carousel.js
553 ms
slider.js
616 ms
fancybox.js
617 ms
custom.js
632 ms
recaptcha__en.js
21 ms
logo.gif
117 ms
bg-k40.png
115 ms
cartouche_tel2.png
117 ms
glyphicons-mini.png
127 ms
01_elegantPlaylist.jpg
244 ms
02_elegantPlaylist.jpg
245 ms
03_elegantPlaylist.jpg
253 ms
05_elegantPlaylist.jpg
363 ms
06_elegantPlaylist.jpg
542 ms
list_star.png
305 ms
conformite2.gif
325 ms
1.png
326 ms
2.png
335 ms
3.png
390 ms
4.png
405 ms
5.png
407 ms
6.png
415 ms
7.png
441 ms
8.png
472 ms
9.png
486 ms
10.png
488 ms
11.png
495 ms
12.png
519 ms
13.png
554 ms
bg-k20.png
567 ms
scroll-top-top.png
569 ms
bg-k10.png
576 ms
list_check.png
597 ms
mifpc.png
622 ms
earthlabel68.png
636 ms
logo_cic.gif
647 ms
SlGVmQWMvZQIdix7AFxXkHNSaBYXags.ttf
79 ms
s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff
619 ms
SlGWmQWMvZQIdix7AFxXmMh3eDs1YiHKpWg.ttf
80 ms
EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff
626 ms
fallback
27 ms
fallback
43 ms
leftNavOFF.png
569 ms
rightNavOFF.png
596 ms
01_elegantPlaylist.jpg
612 ms
02_elegantPlaylist.jpg
616 ms
03_elegantPlaylist.jpg
618 ms
05_elegantPlaylist.jpg
615 ms
06_elegantPlaylist.jpg
631 ms
fallback__ltr.css
4 ms
css
16 ms
logo_48.png
3 ms
scrollerFaceOFF.png
545 ms
hand.cur
561 ms
textBg_transparency.png
559 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
3 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
7 ms
tarteaucitron.css
82 ms
tarteaucitron.en.js
79 ms
tarteaucitron.services.js
81 ms
123-sms.net 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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
123-sms.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
123-sms.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 123-sms.net can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that 123-sms.net 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.
123-sms.net
Open Graph data is detected on the main page of 123 SMS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: