Tools & Wizards About Us
inmag.com screenshot

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

inmag.com

inmag.com - The Los Angeles Magazine of Entertainment, Fashion, People, Lifestyles

Page Load Speed

2.5 sec in total

First Response

330 ms

Resources Loaded

1.8 sec

Page Rendered

391 ms

inmag.com screenshot

About Website

Visit inmag.com now to see the best up-to-date Inmag content and also check out these interesting facts you probably never knew about inmag.com

inmag.com -- The Entertainment, Fashion, People, Lifestyles Magazine of Southern California.

Visit inmag.com

Key Findings

We analyzed Inmag.com page load time and found that the first response time was 330 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

inmag.com performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

96/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

inmag.com

330 ms

home2.gif

185 ms

home1.gif

186 ms

actors2.gif

189 ms

actors1.gif

191 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 95% of them (54 requests) were addressed to the original Inmag.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Inmag.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 17.4 kB (8%)

Content Size

205.3 kB

After Optimization

187.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Inmag.com main page is 205.3 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. Only 10% of websites need less resources to load. Images take 167.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 15.5 kB

  • Original 20.7 kB
  • After minification 20.5 kB
  • After compression 5.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 15.5 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 1.9 kB

  • Original 167.4 kB
  • After minification 165.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. Inmag images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 39 (70%)

Requests Now

56

After Optimization

17

  • Images
  • JavaScript

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inmag. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

inmag.com

inmag.com

330 ms

home2.gif

home2.gif

185 ms

home1.gif

home1.gif

186 ms

actors2.gif

actors2.gif

189 ms

actors1.gif

actors1.gif

191 ms

art2.gif

art2.gif

203 ms

art1.gif

art1.gif

205 ms

books2.gif

books2.gif

254 ms

books1.gif

books1.gif

256 ms

dining2.gif

dining2.gif

256 ms

dining1.gif

dining1.gif

258 ms

film2.gif

film2.gif

258 ms

film1.gif

film1.gif

312 ms

food2.gif

food2.gif

380 ms

food1.gif

food1.gif

381 ms

health2.gif

health2.gif

382 ms

health1.gif

health1.gif

383 ms

mediawatch2.gif

mediawatch2.gif

384 ms

mediawatch1.gif

mediawatch1.gif

436 ms

money2.gif

money2.gif

506 ms

money1.gif

money1.gif

509 ms

music2.gif

music2.gif

509 ms

music1.gif

music1.gif

510 ms

services2.gif

services2.gif

503 ms

services1.gif

services1.gif

555 ms

profiles2.gif

profiles2.gif

904 ms

profiles1.gif

profiles1.gif

905 ms

sports2.gif

sports2.gif

633 ms

sports1.gif

sports1.gif

635 ms

style2.gif

style2.gif

634 ms

style1.gif

style1.gif

682 ms

technology2.gif

technology2.gif

759 ms

technology1.gif

technology1.gif

761 ms

theatre2.gif

theatre2.gif

762 ms

theatre1.gif

theatre1.gif

809 ms

travel2.gif

travel2.gif

885 ms

Logo_25wht.gif

Logo_25wht.gif

14 ms

ga.js

ga.js

8 ms

travel1.gif

travel1.gif

838 ms

__utm.gif

__utm.gif

24 ms

sweet-16.gif

sweet-16.gif

793 ms

music-home-2.jpg

music-home-2.jpg

847 ms

film-home.jpg

film-home.jpg

925 ms

war-dogs.jpg

war-dogs.jpg

915 ms

omar-akram-t.jpg

omar-akram-t.jpg

861 ms

fullstory.gif

fullstory.gif

859 ms

fame.jpg

fame.jpg

875 ms

andrew-weir.jpg

andrew-weir.jpg

909 ms

khloe-kardashian.jpg

khloe-kardashian.jpg

938 ms

money.gif

money.gif

938 ms

wf1.jpg

wf1.jpg

987 ms

brandon-olmos.jpg

brandon-olmos.jpg

939 ms

lake-tahoe.jpg

lake-tahoe.jpg

882 ms

ktla.jpg

ktla.jpg

915 ms

artichoke.gif

artichoke.gif

939 ms

inmags.gif

inmags.gif

938 ms

april2013.jpg

april2013.jpg

1126 ms

Accessibility Review

inmag.com accessibility score

67

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<html> element does not have a [lang] attribute

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

High

Form elements do not have associated labels

Best Practices

inmag.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

inmag.com SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inmag.com 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 Inmag.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.

Social Sharing Optimization

inmag.com

Open Graph description is not detected on the main page of Inmag. 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: