2.8 sec in total
193 ms
2.3 sec
279 ms
Click here to check amazing Someco content. Otherwise, check out these important facts you probably never knew about someco.com.br
Free Bootstrap 4 Pingendo Smke template single landing page team
Visit someco.com.brWe analyzed Someco.com.br page load time and found that the first response time was 193 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
someco.com.br performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value9.0 s
1/100
25%
Value5.4 s
56/100
10%
Value730 ms
40/100
30%
Value0
100/100
15%
Value17.0 s
4/100
10%
193 ms
174 ms
127 ms
60 ms
68 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Someco.com.br, 47% (37 requests) were made to Static.parastorage.com and 22% (17 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (958 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.7 MB (71%)
3.8 MB
1.1 MB
In fact, the total size of Someco.com.br main page is 3.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 115.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. 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 115.0 kB or 85% of the original size.
Potential reduce by 66.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. Obviously, Someco needs image optimization as it can save up to 66.3 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.2 MB
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 2.2 MB or 76% of the original size.
Potential reduce by 246.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. Someco.com.br needs all CSS files to be minified and compressed as it can save up to 246.7 kB or 83% of the original size.
Number of requests can be reduced by 45 (67%)
67
22
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Someco. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
someco.com.br
193 ms
www.someco.com.br
174 ms
bt
127 ms
require.min.js
60 ms
main-r.min.js
68 ms
viewer.css
124 ms
dynamicmodel
51 ms
f5162e_28fd2b146f10fc64b9c24d1d5132db18_684.json.z
321 ms
f5162e_017d8766cc3b749731495ceb132707fe_683.json.z
325 ms
ugc-viewer
46 ms
bt
119 ms
skins.min.js
292 ms
components.min.js
109 ms
utils.min.js
39 ms
core.min.js
107 ms
react-with-addons.min.js
93 ms
lodash.min.js
92 ms
TweenMax.min.js
91 ms
layout.min.js
94 ms
tpa.min.js
96 ms
fonts.min.js
97 ms
animations.min.js
110 ms
swfobject.min.js
115 ms
mousetrap.min.js
115 ms
tweenEngine.min.js
114 ms
DrawSVGPlugin.min.js
103 ms
react-dom.min.js
109 ms
ScrollToPlugin.min.js
112 ms
widgets.min.js
112 ms
experiment.js
112 ms
render.min.js
105 ms
wixappsCore.min.js
273 ms
wixappsClassics.min.js
273 ms
wixappsBuilder.min.js
269 ms
zepto.min.js
97 ms
color.min.js
262 ms
react-dom-server.min.js
33 ms
bt
187 ms
dc.js
160 ms
bt
331 ms
latin.css
322 ms
f5162e_9e6458d075324d5f8a4b23a1576bb3e9.png
482 ms
css
137 ms
f5162e_5a9da44b8d7b4b4b9f13339da420067f.jpg
401 ms
f5162e_ab18f6b34a324167b8897a4e62aad84d.jpg
551 ms
f5162e_58b58cff34bc48c3ba9474e1be6dfa25.jpg
394 ms
f5162e_45b5fda7d002433dab39159b32567652.jpg
550 ms
f5162e_80577e498f384dd9885c7bd2c9a72e2e.jpg
408 ms
f5162e_6e5655f2168c49ea80b821e0042440d5.jpg
750 ms
f5162e_06d36fa80a8e428c80278337769af2e9.jpg
551 ms
f5162e_42445944cbef4906b71f64ca6f7fbc1d.jpg
738 ms
f5162e_8266379785334dbf87a26a6b16afd578.jpg
737 ms
f5162e_4324e19a96a54a6cac1683f1f59bb42d.png
739 ms
f5162e_6305653e33604d34aab01da63505da10.png
802 ms
f5162e_4e2df678fd084e92959e643f3b11ab96.png
765 ms
f5162e_32b6e0dedc41467a9d66b0cc3aed7279.jpg
958 ms
f5162e_23ffe1be445c467a9dd875d9ff1285c2.png
897 ms
bt
110 ms
bt
110 ms
bt
283 ms
shadowbottom.png
122 ms
shiny1button_bg.png
123 ms
arrows_white_new3.png
125 ms
liftedshadow_medium.png
125 ms
Sub_If_x2iU
303 ms
QHna4uyvC5s
393 ms
BaRU3GSISDJW2nIqbysbmg.ttf
160 ms
c5749443-93da-4592-b794-42f28d62ef72.woff
159 ms
b6878f57-4d64-4d70-926d-fa4dec6173a5.woff
160 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
176 ms
ga-audiences
189 ms
ugc-viewer
38 ms
www-embed-player-vflfNyN_r.css
28 ms
www-embed-player.js
56 ms
base.js
94 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
32 ms
ad_status.js
42 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
188 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
187 ms
someco.com.br accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
someco.com.br 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
Page has valid source maps
someco.com.br SEO score
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
Tap targets are not sized appropriately
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Someco.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Someco.com.br 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.
someco.com.br
Open Graph data is detected on the main page of Someco. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: