wweek.com - Willamette Week — Portland News, Movies, Music, Restaurants, Arts

Quick Summary

Online Status

Offline

Server IP address resolved: No
Http response code: None
Last Checked: 01/23/2023

Over the time wweek.com has been ranked as high as 7,368 in the world, while most of its traffic comes from United States, where it reached as high as 8,756 position.

Wweek.com receives about 11,407 unique visitors and 17,111 pageviews per day. The estimated value of wweek.com is 297,840 USD. Each unique visitor makes about 1.5 pageviews on average.

Wweek.com is registered under .COM top-level domain. Check other websites in .COM zone.

At the time of the last check (April 25, 2024) wweek.com has an invalid SSL certificate.

According to Google Safe Browsing, Google Safe Search, Symantec and Web of Trust wweek.com is quite a safe domain.

Mobile-Friendly test indicates that wweek.com is well optimized for mobile and tablet devices, however website page loading time could be improved.

Wweek.com General Information

Global Rank

40,231

Average Load Time

1.37sec

Links In Count

3,761

Website Value

$297,840

Audience Geography. Where are wweek.com visitors located?

Country	Rank
United States US	8756
Norway NO	26270
Canada CA	53863
Australia AU	54613
India IN	181980

Country	Percent of Pageviews
United States US	93.5%
Canada CA	0.9%
Australia AU	0.7%
India IN	0.7%
Norway NO	0.4%
Other	3.9%

Country	Percent of Visitors
United States US	92.2%
Canada CA	1.3%
Australia AU	0.9%
India IN	0.7%
Norway NO	0.6%
Other	4.2%

Where do visitors go on wweek.com?

Subdomain	Pageviews
wweek.com	100%

Subdomain	Pageviews per User
wweek.com	1.5

Subdomain	Reach
wweek.com	100%

How popular is wweek.com?

Days	Reach Rank	Reach Rank Delta	Reach per Million	Reach per Million Delta
90	33884	2340	232	-10.39%
30	40101	9355	19	-25.09%
7	35728	-6367	22	20%
1	34554	1358	23	-4.801%

Days	Pageviews Rank	Pageviews Rank Delta	Pageviews per Million	Pageviews per Million Delta	Pageviews per User	Pageviews per User Delta
90	64202	7683	94	-13.82%	1.5	-3.85%
30	75486	16115	78	-23.43%	1.5	2%
7	68443	-12418	89	20%	1.5	1%
1	76567	-3587	86	6%	1.4	10%

Period	Global Rank	Global Rank Delta
past 3 months	40231	3504
past month	47494	10849
past week	42335	-7548
yesterday	42097	16

Alexa Rank shows how popular wweek.com is in comparison with other sites. The most popular site has Alexa Rank equals 1. If wweek.com has Alexa Rank equals 100,000, then it is in TOP 100,000 popular sites in the world. The rank is calculated using a combination of average daily visitors to wweek.com and pageviews on wweek.com over the past 3 months.

Wweek.com Safety Information

Overview

Last Updated: 04/25/2024

Overall result - "wweek.com" is SAFE.
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.

Norton Connect Safe

Last Updated: 03/22/2024

wweek.com is safe.

Norton ConnectSafe evaluates wweek.com for any unsafe and insecure content. The results are critical for families with young children.

Google Safe Search

Last Updated: 10/17/2016

wweek.com is safe.

SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.

Google Safe Browsing

Last Updated: 01/09/2019

Malware not found at "wweek.com".
"wweek.com" is not a phishing page.
"wweek.com" does not install unwanted software.
"wweek.com" does not contain harmfull applications.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.

Site Advisor

Last Updated: 02/22/2021

wweek.com is safe.

McAfee assesses wweek.com for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze wweek.com for mature or inappropriate content, only security checks are evaluated.

Web of Trust

Last Updated: 01/09/2019

wweek.com child safety isvery good.

The WOT calculates reputation of the wweek.com. This reputation system receives ratings from users and information from third-party sources, assesses the wweek.com for safety features and confirms, whether wweek.com is suitable for children.

SSL Information

SSL Checker Tool

WARNING!	Certificate download error. Previous scan results are shown below.
WARNING!	Wweek.com is not secured by SSL certificate.

Wweek.com Server Information

Server Location

Geolocation Tool

Not Found

ASN Information

ASN Lookup Tool

ASN ID: 14618
ASN Title: AMAZON-AES - Amazon.com, Inc., US

Last Update: 10/03/2023

ASN Whois

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

ASNumber: 14618
ASName: AMAZON-AES
ASHandle: AS14618
RegDate: 2005-11-04
Updated: 2012-03-02
Ref: https://rdap.arin.net/registry/autnum/14618

OrgName: Amazon.com, Inc.
OrgId: AMAZO-4
Address: Amazon Web Services, Inc.
Address: P.O. Box 81226
City: Seattle
StateProv: WA
PostalCode: 98108-1226
Country: US
RegDate: 2005-09-29
Updated: 2017-01-28
Comment: For details of this service please see
Comment: http://ec2.amazonaws.com/
Ref: https://rdap.arin.net/registry/entity/AMAZO-4

OrgNOCHandle: AANO1-ARIN
OrgNOCName: Amazon AWS Network Operations
OrgNOCPhone: +1-206-266-4064
OrgNOCEmail: amzn-noc-contact@amazon.com
OrgNOCRef: https://rdap.arin.net/registry/entity/AANO1-ARIN

OrgTechHandle: ANO24-ARIN
OrgTechName: Amazon EC2 Network Operations
OrgTechPhone: +1-206-266-4064
OrgTechEmail: amzn-noc-contact@amazon.com
OrgTechRef: https://rdap.arin.net/registry/entity/ANO24-ARIN

OrgAbuseHandle: AEA8-ARIN
OrgAbuseName: Amazon EC2 Abuse
OrgAbusePhone: +1-206-266-4064
OrgAbuseEmail: abuse@amazonaws.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/AEA8-ARIN

RTechHandle: ANO24-ARIN
RTechName: Amazon EC2 Network Operations
RTechPhone: +1-206-266-4064
RTechEmail: amzn-noc-contact@amazon.com
RTechRef: https://rdap.arin.net/registry/entity/ANO24-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

Wweek.com Domain Name Information

WHOIS

WHOIS Lookup Tool

Domain Whois

Domain Name: WWEEK.COM
Registry Domain ID: 1489899_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.register.com
Registrar URL: http://www.register.com
Updated Date: 2021-03-25T08:57:07Z
Creation Date: 1995-04-23T04:00:00Z
Registry Expiry Date: 2022-04-24T04:00:00Z
Registrar: Register.com, Inc.
Registrar IANA ID: 9
Registrar Abuse Contact Email: abuse@web.com
Registrar Abuse Contact Phone: +1.8003337680
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.CANVASHOST.COM
Name Server: NS2.CANVASHOST.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-04-26T21:29:58Z

DNS Records

DNS Lookup Tool

Host	A Record	TTL

Host	MX Record	Priority	TTL

Host	NS Record	TTL

Host	TXT Record	TTL

Wweek.com HTML Validation

HTML Validation Tool

Errors

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Attribute “name” not allowed on element “meta” at this point.

Attribute “value” not allowed on element “meta” at this point.

Element “meta” is missing required attribute “content”.

Element “meta” is missing one or more of the following attributes: “content”, “property”.

Attribute “property” not allowed on element “meta” at this point.

Bad start tag in “img” in “head”.

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Stray end tag “noscript”.

Stray end tag “head”.

Start tag “body” seen but an element of the same type was already open.

Element “a” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

Bad value “text-field” for attribute “type” on element “input”.

Element “img” is missing required attribute “src”.

Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)

Bad value “December 4 at 6:11 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 4 at 5:35 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 4 at 4:47 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 4 at 4:13 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 4 at 3:17 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 4 at 1:18 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 4 at 10:07 AM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 4 at 8:16 AM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 3 at 9:11 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 3 at 8:20 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 3 at 3:02 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 3 at 2:12 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 2 at 3:18 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 2 at 11:03 AM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 1 at 2:16 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 1 at 1:11 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “December 1 at 12:48 PM” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Element “span” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

Duplicate ID “flex_”.

Bad value “” for attribute “src” on element “img”: Must be non-empty.

Bad value “https://www.facebook.com/tr?id=1955258371407056&ev=PageView &noscript=1” for attribute “src” on element “img”: Illegal character in query: space is not allowed.

Warnings

The first occurrence of ID “flex_” was here.

Empty heading.

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

This document appears to be written in English. Consider adding “lang="en"” (or variant) to the “html” start tag.

Wweek.com Desktop Insights

Desktop Page Insights Tool

Last tested: 12/12/2019

Desktop

Desktop Speed

Optimize images

Enable compression

Leverage browser caching

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Avoid landing page redirects

Minify JavaScript

Prioritize visible content

Desktop Resource Breakdown

Total Resources	106
Number of Hosts	35
Static Resources	64
JavaScript Resources	40
CSS Resources	5

Wweek.com Mobile Insights

Mobile Page Insights Tool

Last tested: 05/20/2017

Mobile

Mobile Usability

99%

Size tap targets appropriately

Mobile Speed

44%

Optimize images

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Avoid landing page redirects

Prioritize visible content

Leverage browser caching

Reduce server response time

Mobile Resource Breakdown

Total Resources	104
Number of Hosts	31
Static Resources	58
JavaScript Resources	37
CSS Resources	4

Wweek.com Typos

www.wweek.com
www.wweek.net
www.wweek.org
www.wweek.info
www.wweek.biz
www.wweek.us
www.wweek.mobi
www.week.com
www.wweek.com
www.qweek.com
www.wqweek.com
www.qwweek.com
www.aweek.com
www.waweek.com
www.awweek.com
www.sweek.com
www.wsweek.com
www.swweek.com
www.eweek.com
www.weweek.com
www.ewweek.com
www.wqeek.com
www.wwqeek.com
www.waeek.com
www.wwaeek.com
www.wseek.com
www.wwseek.com
www.weeek.com
www.wweeek.com
www.wwek.com
www.wwwek.com
www.wwewek.com
www.wwweek.com
www.wwsek.com
www.wwesek.com
www.wwdek.com
www.wwedek.com
www.wwdeek.com
www.wwrek.com
www.wwerek.com
www.wwreek.com
www.wwewk.com
www.wweewk.com
www.wwesk.com
www.wweesk.com
www.wwedk.com
www.wweedk.com
www.wwerk.com
www.wweerk.com
www.wwee.com
www.wweej.com
www.wweekj.com
www.wweejk.com
www.wweei.com
www.wweeki.com
www.wweeik.com
www.wweem.com
www.wweekm.com
www.wweemk.com
www.wweel.com
www.wweekl.com
www.wweelk.com
www.wweeo.com
www.wweeko.com
www.wweeok.com
www.wweek.con

Wweek.com Willamette Week — Portland News, Movies, Music, Restaurants, Arts

Quick Summary

Wweek.com General Information

Wweek.com Alexa Rank History

Wweek.com Safety Information

Wweek.com Server Information

Wweek.com Domain Name Information

Wweek.com HTML Validation

Wweek.com Desktop Insights

Wweek.com Mobile Insights

Wweek.com Nearest Competitors

Wweek.com Typos