5 sec in total
257 ms
1.1 sec
3.7 sec
Welcome to smilesquare.com homepage info - get ready to check Smilesquare best content right away, or after learning these important things about smilesquare.com
Visit smilesquare.comWe analyzed Smilesquare.com page load time and found that the first response time was 257 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
smilesquare.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value6.1 s
12/100
25%
Value4.2 s
78/100
10%
Value1,660 ms
11/100
30%
Value0.078
95/100
15%
Value9.4 s
31/100
10%
257 ms
40 ms
84 ms
38 ms
51 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 88% of them (60 requests) were addressed to the original Smilesquare.com, 7% (5 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (501 ms) belongs to the original domain Smilesquare.com.
Page size can be reduced by 291.6 kB (29%)
999.5 kB
707.9 kB
In fact, the total size of Smilesquare.com main page is 999.5 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. 55% of websites need less resources to load. Images take 717.5 kB which makes up the majority of the site volume.
Potential reduce by 33.5 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 33.5 kB or 86% of the original size.
Potential reduce by 87.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. Obviously, Smilesquare needs image optimization as it can save up to 87.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 99.9 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 99.9 kB or 68% of the original size.
Potential reduce by 70.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. Smilesquare.com needs all CSS files to be minified and compressed as it can save up to 70.7 kB or 73% of the original size.
Number of requests can be reduced by 5 (8%)
61
56
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smilesquare. 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.
smilesquare.com
257 ms
wp-emoji-release.min.js
40 ms
css
84 ms
genericons.css
38 ms
style.css
51 ms
jquery.js
64 ms
jquery-migrate.min.js
36 ms
skip-link-focus-fix.js
124 ms
functions.js
125 ms
wp-embed.min.js
137 ms
448965d46cd5587cc938e746fb08838f
346 ms
1-1.png
322 ms
2-4-232x300.jpg
324 ms
3-4-222x300.jpg
328 ms
4-232x300.png
331 ms
5-300x236.gif
326 ms
1-3.jpg
320 ms
2-3.jpg
341 ms
3-3-232x300.jpg
335 ms
4-4-232x300.jpg
336 ms
6.jpg
331 ms
1-2-254x300.jpg
341 ms
2-2-232x300.jpg
345 ms
3-2-232x300.jpg
349 ms
4-3.jpg
338 ms
5-212x300.png
408 ms
1-1.jpg
340 ms
2-1-254x300.jpg
409 ms
3-1-212x300.jpg
407 ms
4-2-232x300.jpg
407 ms
5-2-232x300.jpg
427 ms
1.jpg
408 ms
2-232x300.jpg
427 ms
3-212x300.jpg
425 ms
4-1-214x300.jpg
424 ms
5-1.jpg
422 ms
1.png
480 ms
2-232x300.png
492 ms
3-232x300.png
495 ms
4-250x300.jpg
500 ms
5.jpg
484 ms
i1.png
482 ms
i2.jpg
491 ms
i3.jpg
501 ms
RFda8w1V0eDZheqfcyQ4EI3LH2FgLjViKkqswU-xtII.ttf
410 ms
ZvcMqxEwPfh2qDWBPxn6npK87lA5VkoZ9MEfk0lvEWI.ttf
470 ms
ZvcMqxEwPfh2qDWBPxn6ntIoQl57Hlnr-S18thSTvQ4.ttf
479 ms
i4.jpg
484 ms
i5.jpg
217 ms
h1.jpg
217 ms
IQHow_FEYlDC4Gzy_m8fcsBaWKZ57bY3RXgXH6dOjZ0.ttf
193 ms
zhcz-_WihjSQC0oHJ9TCYMDdSZkkecOE1hvV7ZHvhyU.ttf
191 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
46 ms
Genericons.svg
295 ms
h2.jpg
205 ms
h3.jpg
203 ms
h4.jpg
203 ms
h5.jpg
283 ms
g1.jpg
278 ms
g2.png
277 ms
g3.jpg
280 ms
g4.png
279 ms
g5.png
277 ms
l1-1.png
280 ms
l2-3-193x300.jpg
277 ms
l3-2-232x300.jpg
278 ms
l4-2.jpg
273 ms
l5-2-233x300.jpg
271 ms
smilesquare.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
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
Links do not have a discernible name
smilesquare.com 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
smilesquare.com SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Smilesquare.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 Smilesquare.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.
smilesquare.com
Open Graph description is not detected on the main page of Smilesquare. 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: