Uconn.edu - SEO Checker - Website Review

Your Website Score is

Similar Ranking

NEW CARS, USED CARS, CAR DEALERS, PRICES & REVIEWS | CARS.COM

cars.com

DELFI ŽINIOS - PAGRINDINIS NAUJIENŲ PORTALAS LIETUVOJE

delfi.lt

NTTコミュニケーションズ　オフィシャルサイト

ntt.com

ギズモード・ジャパン | 日本最大級のガジェット＆テクノロジーサイト

gizmodo.jp

SCOOPWHOOP

scoopwhoop.com

BALENCIAGA OFFICIAL ONLINE BOUTIQUE

balenciaga.com

PRZYJAZNY DYSK INTERNETOWY - CHOMIKUJ.PL

chomikuj.pl

Latest Sites

PORTSTONE PARTNERS LIMITED

portstonepartnersltd.com

VENICTRADE.COM

venictrade.com

COINLUNO.COM

coinluno.com

SIGNCURRENCY.COM

signcurrency.com

ALLTRADESFX.COM

alltradesfx.com

MODERN KITCHENS | READIKIT | HOME PAGE

readikit.com

av4.xyz

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

70 uconn.edu Last Updated: 9 months

Success 70% of passed verification steps

Warning 23% of total warning

Errors 7% of total errors, require fast action

Mobile

Performance Desktop Score 81%

Best Practices Desktop Score 69%

SEO Desktop Score 82%

Progressive Web App Desktop Score 31%

Performance Mobile Score 39%

Best Practices Mobile Score 69%

SEO Mobile Score 81%

Progressive Web App Mobile Score 33%

Page Authority Authority 64%

Domain Authority Domain Authority 78%

Moz Rank 6.4/10

Bounce Rate Rate 0%

Title Tag 53 Characters

UNIVERSITY OF CONNECTICUT | UNIVERSITY OF CONNECTICUT

Meta Description 155 Characters

UConn’s First Rhodes Scholar: Wanjiku Gatheru ’20 (CAHNR) UConn Today UConn’s First Rhodes Scholar: Wanjiku Gatheru ’20 (CAHNR)...

Effective URL 17 Characters

https://uconn.edu

Excerpt Page content

University of Connecticut | University of Connecticut Our websites may use cookies to personalize and enhance your experience. By continuing without changing your cookie settings, you agree to this collection. For more information, pleas...

Keywords Cloud Density

uconn29 campus15 visit12 students10 research9 more8 connecticut7 about6 university6 admissions6

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
uconn	29
campus	15
visit	12
students	10
research	9
more	8
connecticut	7
about	6
university	6
admissions	6

Google Preview Your look like this in google search result

UNIVERSITY OF CONNECTICUT | UNIVERSITY OF CONNECTICUT

https://uconn.edu

UConn’s First Rhodes Scholar: Wanjiku Gatheru ’20 (CAHNR) UConn Today UConn’s First Rhodes Scholar: Wanjiku Gatheru ’20 (CAHN

Robots.txt File Detected

http://uconn.edu/robots.txt

Sitemap.xml File Detected

http://uconn.edu/sitemap.xml

Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system

Updated: 1970-01-01 / 51 years

Create on: 1970-01-01 / 51 years

Expires on: 1970-01-01 / 618 months 14 days

Page Size Code & Text Ratio

Document Size: ~67.28 KB

Code Size: ~60.45 KB

Text Size: ~6.83 KB Ratio: 10.16%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Manifest is not valid

Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Remove unused CSS Potential savings of 154 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 1,889 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

User Timing marks and measures 3 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Reduce server response times (TTFB) Root document took 1,250 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 140 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 55 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Efficiently encode images Potential savings of 258 KB

Optimized images load faster and consume less cellular data

Reduce the impact of third-party code Third-party code blocked the main thread for 260 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 350 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 1.4 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Server Backend Latencies 0 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

Speed Index 1.9 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 2.9 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoid enormous network payloads Total size was 4,250 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 2.3 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 0.7 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 20 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load

Avoids an excessive DOM size 728 elements

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

Preload key requests Potential savings of 420 ms

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

First Meaningful Paint 1.1 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 65 requests • 4,251 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 11 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 210 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 3.0 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Links do not have descriptive text 1 link found

Descriptive link text helps search engines understand your content

Network Round Trip Times 0 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

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 13.7 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 60 ms

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

Mobile

Tap targets are not sized appropriately 56% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

Document uses legible font sizes 97.83% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

Remove unused CSS Potential savings of 155 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 1,620 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

User Timing marks and measures 3 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Reduce server response times (TTFB) Root document took 1,170 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 280 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 55 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Reduce the impact of third-party code Third-party code blocked the main thread for 1,300 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 2,270 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 5.5 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Defer offscreen images Potential savings of 2,142 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Server Backend Latencies 0 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

Speed Index 6.1 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 12.0 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoid enormous network payloads Total size was 3,582 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 8.0 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 2.3 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 20 chains found

Avoids an excessive DOM size 728 elements

Preload key requests Potential savings of 4,410 ms

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

First Meaningful Paint 4.3 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 64 requests • 3,583 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 10 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 750 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 12.6 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Links do not have descriptive text 1 link found

Descriptive link text helps search engines understand your content

Network Round Trip Times 0 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

Page load is not fast enough on mobile networks Interactive at 12.6 s

A fast page load over a cellular network ensures a good mobile user experience

First Contentful Paint (3G) 4971 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Estimated Input Latency 330 ms

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Server: nginx/1.10.3
Date: Thu, 16 Jan 2020 10:00:06 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
X-Powered-By: W3 Total Cache/0.12.0
Link: ; rel=shortlink
Set-Cookie: PHPSESSID=97d4a6c776b4a5744a32bb5e320d14c3; path=/

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	uconn.edu	137.99.26.48	IN	1
NS	uconn.edu	hbl-cache.net.uconn.edu	IN	33961
NS	uconn.edu	dr-dns.net.uconn.edu	IN	33961
NS	uconn.edu	msb-cache.net.uconn.edu	IN	33961
MX	uconn.edu	uconn-edu.mail.protection.outlook.com	IN	180
TXT	uconn.edu	google-site-verification=BUtdK87WS2puV-Elv787vJLN0ETGl0MPf2jqfwMgDuo	IN	3600
TXT	uconn.edu	Mwj1qwM8tOAajB6bTqUVcfttE9gBqoElAaNZKQSmPmbvZX5F3dlqmITLR0IcBditndHO7gPCQdJq9g0FY0WqZA==	IN	3600
TXT	uconn.edu	MS=ms60238737	IN	3600
TXT	uconn.edu	atlassian-domain-verification=Q60jr4Czt7k5dZSXe2SJz9apC3TROZmqmR7Gmjp40qkYgeBW8ItVnXlv38RW8sB3	IN	3600
TXT	uconn.edu	google-site-verification=tViaPVU5yYasYiCo_SFOj5DDV0aUbGc1gI_GVd6MRmk	IN	3600
TXT	uconn.edu	lrulkn3u1s53q6vdmp3haoj90i	IN	3600
TXT	uconn.edu	v=spf1 include:_spf1.uconn.edu include:spf.protection.outlook.com include:_spf.google.com ~all	IN	3600
TXT	uconn.edu	adobe-idp-site-verification=8d8d7ca16093b79815399bece310037e85d272bcb52ad13ed2404151287bc7e8	IN	3600

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

70 uconn.edu Last Updated: 9 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Google Font API

Google Tag Manager

Nginx

PHP

W3 Total Cache

WordPress

YouTube

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments