4.1 sec in total
196 ms
2.8 sec
1.1 sec
Visit indyweek.com now to see the best up-to-date INDY Week content for United States and also check out these interesting facts you probably never knew about indyweek.com
Read the latest news, culture, music, and progressive commentary in Raleigh, Durham, Chapel Hill and across the Triangle and North Carolina.
Visit indyweek.comWe analyzed Indyweek.com page load time and found that the first response time was 196 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
indyweek.com performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value2.7 s
85/100
25%
Value17.2 s
0/100
10%
Value13,760 ms
0/100
30%
Value0.42
23/100
15%
Value36.1 s
0/100
10%
196 ms
249 ms
123 ms
128 ms
186 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 19% of them (22 requests) were addressed to the original Indyweek.com, 22% (26 requests) were made to Media1.fdncms.com and 16% (19 requests) were made to Media2.fdncms.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Media1.fdncms.com.
Page size can be reduced by 875.2 kB (36%)
2.5 MB
1.6 MB
In fact, the total size of Indyweek.com main page is 2.5 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. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 187.4 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 46.9 kB, which is 21% 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 187.4 kB or 85% of the original size.
Potential reduce by 78.5 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. INDY Week images are well optimized though.
Potential reduce by 434.1 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 434.1 kB or 61% of the original size.
Potential reduce by 175.1 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. Indyweek.com needs all CSS files to be minified and compressed as it can save up to 175.1 kB or 84% of the original size.
Number of requests can be reduced by 44 (40%)
110
66
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INDY Week. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
indyweek.com
196 ms
www.indyweek.com
249 ms
reset.css
123 ms
defaults.css
128 ms
components.css
186 ms
publication.css
126 ms
eibon-11-zone.css
138 ms
core-public.js
306 ms
jquery.fancybox-1.3.4.css
183 ms
ntwXoruhEeSyCg4AfQhyIQ.js
16 ms
conversion.js
32 ms
quant.js
6 ms
js
8 ms
css
46 ms
css
54 ms
css
133 ms
gpt.js
283 ms
analytics.js
291 ms
fbds.js
275 ms
285 ms
twitter-logo-24.png
284 ms
facebook-logo-24.png
428 ms
D1.jpg
164 ms
facebook_icon_46px.jpg
233 ms
twitter_icon_46px.png
134 ms
instagram_icon_46px.png
135 ms
vimeo-logo-24.png
253 ms
_sexhandcuffs-cover.jpg
398 ms
2.10_screen_deadpool.jpg
436 ms
voivod2.jpg
253 ms
420c6deb_1hackensack_dreaming_detail_b.jpg
252 ms
15ab160b_pull-publicity_image.jpg
476 ms
_sexhandcuffs-cover.jpg
698 ms
sexhudnall.jpg
655 ms
cartoon-baby-funny-vector-material-03.jpg
587 ms
_mccrory.jpg
697 ms
_sexhandcuffs-cover.jpg
696 ms
sexhudnall.jpg
697 ms
cartoon-baby-funny-vector-material-03.jpg
856 ms
_mccrory.jpg
910 ms
_triangulator.jpg
993 ms
_softreturn.jpg
909 ms
2.10_screen_deadpool.jpg
992 ms
160209_mother_earth_026.jpg
992 ms
g_.png
389 ms
rss-logo-24.png
388 ms
160206_publix_013.jpg
467 ms
public-safety-is-none-of-your.jpg
467 ms
bowsers.jpg
466 ms
160204_tomjennys_028.jpg
853 ms
gerrymander.png
664 ms
screen_shot_2016-02-15_at_3.46.03_pm.png
661 ms
gerrymander.png
661 ms
img_3903.jpg
658 ms
finder2015bulletin.jpg
872 ms
2.3_art-cal-spot_public-display-2.jpg
869 ms
10.28_art-cal_jon-lowenstein.jpg
870 ms
10.21_art-cal_treasures-of-carolina.jpg
870 ms
_sexswingers.jpg
954 ms
160206_bdsm_095.jpg
1088 ms
_anncoulter.jpg
1134 ms
_sexhandcuffs.jpg
1118 ms
_sexswingers.jpg
990 ms
160206_bdsm_095.jpg
979 ms
_anncoulter.jpg
1118 ms
_sexhandcuffs.jpg
1163 ms
150520_ab_indy_heirloomseeds_0163_1_.jpg
1139 ms
02.10musled_gyama2_photobyryancocca.jpg.jpg
1191 ms
2.10_stage_lion-king.jpg
1208 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
110 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
109 ms
pubads_impl_80.js
94 ms
283 ms
collect
174 ms
collect
381 ms
410 ms
collect
206 ms
363 ms
410 ms
431 ms
print.css
222 ms
container.html
257 ms
sdk.js
224 ms
ads
294 ms
new-indy-logo.png
204 ms
123 ms
search-btn.gif
94 ms
xd_arbiter.php
54 ms
xd_arbiter.php
101 ms
ads
46 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
40 ms
2-16_Indy_Digital-Billboard_Ad2.jpg
266 ms
INDY-Weeks-2016-Best-of-the-Triangle-nominations
409 ms
13867192244130444005
88 ms
ads
85 ms
osd.js
124 ms
more.png
201 ms
quote.gif
168 ms
calendar
164 ms
7870061145536038484
81 ms
ads
74 ms
11281616947024321866
37 ms
mag-icon.gif
125 ms
features-icon_video.gif
119 ms
ads
224 ms
icon_rss.gif
93 ms
pixel;r=1381238622;a=p-7apeS9pNVYMQo;fpan=1;fpa=P0-1890903368-1455636592150;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1455636592149;tzo=-180;ref=;url=http%3A%2F%2Fwww.indyweek.com%2F;ogl=url.http%3A%2F%2Fwww%252Eindyweek%252Ecom%2F%2Csite_name.Indy%20Week%2Ctitle.Indy%20Week%2Cimage.http%3A%2F%2Fwww%252Eindyweek%252Ecom%2Fbinary%2F06e2%2Findy-logo-sq-fb%252Epng%2Cdescription.Progressive%20news%252C%20culture%20and%20commentary%20for%20Raleigh%252C%20Cary%252C%20Durham%20and%20Chapel%20Hi%2Ctype.website
85 ms
cx.js
77 ms
in.php
274 ms
p1.html
5 ms
p1.js
9 ms
rep.gif
4 ms
xd_arbiter.php
7 ms
fpi.js
8 ms
sync
18 ms
adcfg
10 ms
indyweek.com 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.
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
indyweek.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
indyweek.com 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indyweek.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Indyweek.com 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.
indyweek.com
Open Graph data is detected on the main page of INDY Week. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: