8.7 sec in total
1.9 sec
6.6 sec
161 ms
Welcome to portal.weg.net homepage info - get ready to check Portal Weg best content for Brazil right away, or after learning these important things about portal.weg.net
Visit portal.weg.netWe analyzed Portal.weg.net page load time and found that the first response time was 1.9 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
portal.weg.net performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value2.8 s
82/100
25%
Value11.4 s
5/100
10%
Value490 ms
59/100
30%
Value0
100/100
15%
Value9.8 s
28/100
10%
1920 ms
709 ms
506 ms
329 ms
511 ms
Our browser made a total of 25 requests to load all elements on the main page. We found that all of those requests were addressed to Portal.weg.net and no external sources were called. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Portal.weg.net.
Page size can be reduced by 74.5 kB (51%)
145.4 kB
70.9 kB
In fact, the total size of Portal.weg.net main page is 145.4 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. 15% of websites need less resources to load. Images take 81.3 kB which makes up the majority of the site volume.
Potential reduce by 5.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. This page needs HTML code to be minified as it can gain 1.4 kB, which is 18% 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 5.6 kB or 74% of the original size.
Potential reduce by 21.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, Portal Weg needs image optimization as it can save up to 21.3 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 30.2 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 30.2 kB or 85% of the original size.
Potential reduce by 17.3 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. Portal.weg.net needs all CSS files to be minified and compressed as it can save up to 17.3 kB or 84% of the original size.
We found no issues to fix!
22
22
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Portal Weg. According to our analytics all requests are already optimized.
portal.weg.net
1920 ms
portal.weg.net
709 ms
index.html
506 ms
caxtonstyle.css
329 ms
resources.js
511 ms
nsshare.js
683 ms
login.js
524 ms
LoginButtonRolloverGlow.gif
170 ms
ctxHeader01.gif
166 ms
ctxHeader02.gif
498 ms
NavBarLink.gif
181 ms
CenterBlueBkg.jpg
516 ms
LoginCarbonFiberBgFooter.gif
338 ms
LoginPaneTopLeftBorderGlow.png
350 ms
LoginPaneTopMidBorderGlow.png
502 ms
LoginPaneTopRightBorderGlow.png
519 ms
LoginPaneCenterLeftBorderGlow.png
522 ms
LoginPaneCenterMidGlow.png
548 ms
LoginIcon.png
830 ms
LoginButtonGlow.gif
664 ms
LoginPaneCenterRightBorderGlow.png
687 ms
LoginPaneFooterLeftBorderGlow.png
688 ms
LoginPaneFooterMidBorderGlow.png
689 ms
LoginPaneFooterRightBorderGlow.png
729 ms
CitrixWatermark.gif
826 ms
portal.weg.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
portal.weg.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
portal.weg.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Portal.weg.net 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 Portal.weg.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.
portal.weg.net
Open Graph description is not detected on the main page of Portal Weg. 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: