Puc-rio.br Site Title

PUC-Rio - Pontifícia Universidade Católica do Rio de Janeiro

Puc-rio.br Meta Description

Visite o site da Pontifícia Universidade Católica do Rio de Janeiro - PUC-Rio! Informações sobre as atividades da Universidade: Ensino e Pesquisa, Cursos de Graduação e Pós-Graduação, Projetos de Educação a Distância, Vestibular, Intercâmbio Internacional, Cursos de Extensão. E mais: serviços para a comunidade e publicações on-line!

Puc-rio.br Test Results

Puc-rio.br Mobile Performance: 52/100
Quick overview:
First Meaningful Paint
6.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
9.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
190 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Server Backend Latencies
200 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Metrics
Collects all available metrics.
Diagnostics
Collection of useful page vitals.
Script Treemap Data
Used for treemap app
Final Screenshot
The last screenshot captured of the pageload.

1117441333892

Network Round Trip Times
30 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Network Requests
Lists the network requests that were made during page load.

Puc-rio.br Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Puc-rio.br Mobile Best Practices: 64/100
Quick overview:
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document contains a `doctype` that triggers `limited-quirks-mode`
Puc-rio.br Mobile PWA: 38/100
Quick overview:
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens. Failures: No manifest was fetched.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.
Puc-rio.br Mobile Accessibility: 68/100
Quick overview:
Document has a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Select elements do not have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Image elements have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Best practices
These items highlight common accessibility best practices.
The document uses `<meta http-equiv="refresh">`
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar sites
Similar tests
www.puc-rio.com
www.puc-rio.net
www.puc-rio.org
www.puc-rio.info
www.puc-rio.biz
www.puc-rio.us
www.puc-rio.mobi
www.uc-rio.br
www.puc-rio.br
www.ouc-rio.br
www.pouc-rio.br
www.opuc-rio.br
www.luc-rio.br
www.pluc-rio.br
www.lpuc-rio.br
www.pc-rio.br
www.pyc-rio.br
www.puyc-rio.br
www.pyuc-rio.br
www.phc-rio.br
www.puhc-rio.br
www.phuc-rio.br
www.pjc-rio.br
www.pujc-rio.br
www.pjuc-rio.br
www.pic-rio.br
www.puic-rio.br
www.piuc-rio.br
www.pu-rio.br
www.pux-rio.br
www.pucx-rio.br
www.puxc-rio.br
www.pud-rio.br
www.pucd-rio.br
www.pudc-rio.br
www.puf-rio.br
www.pucf-rio.br
www.pufc-rio.br
www.puv-rio.br
www.pucv-rio.br
www.puvc-rio.br
www.pucrio.br
www.puc-io.br
www.puc-eio.br
www.puc-reio.br
www.puc-erio.br
www.puc-dio.br
www.puc-rdio.br
www.puc-drio.br
www.puc-fio.br
www.puc-rfio.br
www.puc-frio.br
www.puc-tio.br
www.puc-rtio.br
www.puc-trio.br
www.puc-ro.br
www.puc-ruo.br
www.puc-riuo.br
www.puc-ruio.br
www.puc-rjo.br
www.puc-rijo.br
www.puc-rjio.br
www.puc-rko.br
www.puc-riko.br
www.puc-rkio.br
www.puc-roo.br
www.puc-rioo.br
www.puc-roio.br
www.puc-ri.br
www.puc-rii.br
www.puc-rioi.br
www.puc-riio.br
www.puc-rik.br
www.puc-riok.br
www.puc-ril.br
www.puc-riol.br
www.puc-rilo.br
www.puc-rip.br
www.puc-riop.br
www.puc-ripo.br
Last Tested: