6.5 sec in total
812 ms
5.3 sec
368 ms
Click here to check amazing SOL content for Portugal. Otherwise, check out these important facts you probably never knew about sol.pt
As notícias e a opinião que interessam. todos os dias, a todas as horas no Nascer do SOL em sol.pt
Visit sol.ptWe analyzed Sol.pt page load time and found that the first response time was 812 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
sol.pt performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value12.2 s
0/100
25%
Value8.4 s
18/100
10%
Value1,010 ms
27/100
30%
Value0.091
92/100
15%
Value17.6 s
4/100
10%
812 ms
224 ms
227 ms
230 ms
348 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 32% of them (35 requests) were addressed to the original Sol.pt, 15% (16 requests) were made to Cdn2.sol.pt and 14% (15 requests) were made to Cdn1.sol.pt. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Sol.pt.
Page size can be reduced by 827.7 kB (70%)
1.2 MB
361.6 kB
In fact, the total size of Sol.pt main page is 1.2 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. 70% of websites need less resources to load. Javascripts take 626.6 kB which makes up the majority of the site volume.
Potential reduce by 311.6 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 311.6 kB or 80% of the original size.
Potential reduce by 16.0 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, SOL needs image optimization as it can save up to 16.0 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 426.3 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 426.3 kB or 68% of the original size.
Potential reduce by 73.9 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. Sol.pt needs all CSS files to be minified and compressed as it can save up to 73.9 kB or 87% of the original size.
Number of requests can be reduced by 38 (39%)
98
60
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SOL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
sol.pt
812 ms
reset.css
224 ms
flaticon.css
227 ms
reveal.css
230 ms
sol_styleV14.css
348 ms
modernizr.custom.16531.js
389 ms
jquery-1.11.0.min.js
561 ms
jquery.isotope.min.js
228 ms
jquery.isotope.perfectmasonry.js
231 ms
jquery.reveal.js
230 ms
jquery.mousewheel.min.js
388 ms
sol_vertical.js
389 ms
utils_v15.js
390 ms
analytics.js
49 ms
prum.min.js
8 ms
netscope-gemius.js
1561 ms
gpt.js
6 ms
menutop.png
504 ms
513347.jpg
753 ms
activity
307 ms
pct
619 ms
loading.gif
345 ms
noimg.jpg
346 ms
LogoSol.png
526 ms
learn
305 ms
sdk.js
37 ms
pubads_impl_81.js
34 ms
513284.png
497 ms
headaerultimas.png
305 ms
513355.jpg
641 ms
513337.jpg
487 ms
flaticon.woff
303 ms
montserrat-regular-webfont.woff
301 ms
linkid.js
54 ms
ads
457 ms
container.html
21 ms
513365.jpg
391 ms
513363.png
548 ms
513351.jpg
391 ms
513252.jpg
392 ms
513294.jpg
398 ms
513242.jpg
510 ms
513338.png
543 ms
542 ms
collect
137 ms
collect
364 ms
xd_arbiter.php
175 ms
xd_arbiter.php
214 ms
Home
460 ms
expansion_embed.js
19 ms
m_js_controller.js
72 ms
favicon
136 ms
abg.js
86 ms
googlelogo_color_112x36dp.png
84 ms
nessie_icon_thin_arrow_big_white.png
117 ms
osd.js
25 ms
like.php
178 ms
s
44 ms
x_button_blue2.png
7 ms
qbEHJxuVK5u.js
23 ms
LVx-xkvaJ0b.png
10 ms
hopiniao.jpg
283 ms
513247.jpg
368 ms
513341.jpg
275 ms
2
416 ms
513292.jpg
119 ms
513286.jpg
121 ms
513326.png
129 ms
513361.jpg
349 ms
513332.png
536 ms
513345.jpg
359 ms
513335.jpg
535 ms
513297.png
233 ms
513300.jpg
124 ms
513296.jpg
119 ms
513316.jpg
126 ms
513368.jpg
360 ms
513358.jpg
241 ms
camera.png
119 ms
bgopiniao.jpg
120 ms
jose_antonio_saraiva.png
122 ms
jose_antonio_lima.png
1146 ms
ana_paula_azevedo.png
116 ms
mario_crespo.png
121 ms
sofia_vala_rocha.png
229 ms
pedro_danunciacao.png
2771 ms
5171746271700867932
53 ms
Index
2325 ms
Index
1282 ms
Index
957 ms
Index
558 ms
xlgemius.js
515 ms
4
1593 ms
513350.png
127 ms
513343.jpg
126 ms
activeview
12 ms
fpdata.js
132 ms
lsget.html
253 ms
activeview
13 ms
Index
790 ms
rexdot.js
134 ms
513357.jpg
152 ms
513353.jpg
125 ms
513331.jpg
367 ms
513325.jpg
126 ms
513322.jpg
118 ms
513320.jpg
121 ms
Index
363 ms
sol.pt 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
The document uses <meta http-equiv="refresh">
sol.pt 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
sol.pt 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
![]()
PT
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sol.pt 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 Sol.pt 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.
sol.pt
Open Graph data is detected on the main page of SOL. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: