Since Google is going to soon update their index regarding mobile readiness (again), have you put in extra effort to make it mobile friendly?
No, since mine have had responsive elastic semi-fluid layout since before responsive was a thing; first I was using the scripting trick called "mcSwitchy" (or a variation I called quickswitchy) that when media queries came along, it was a simple matter of swapping the scripting for those. THAT and I used layout techniques DESIGNED to gracefully degrade and be able to re-arrange/remove columns dating back nearly fifteen years now, meaning adding responsiveness to already elastic and semi-fluid layout is a ten minute job taking maybe 2k of CSS. You have to put more time than that into it, there is something horribly and terrifyingly WRONG with your HTML, CSS, JavaScript, and/or design! Sadly these days it's all four being utterly banjaxed seeing how far up 1997's arse everyone has their heads wedged in terms of markup and accessibility! -- see websites that put black text over images with black in them so you can't actually read it... or that waste an entire screen-height on some goofy stock image completely unrelated to the SUBJECT of the bloody page pushing anything resembling CONTENT clear off the screen... Or websites where the person who wrote it doesn't know what's wrong with this: <body class="home page-template-default page page-id-16 wp-custom-logo twentyseventeen-front-page has-header-image page-one-column colors-dark"> <div id="page" class="site"> <a class="skip-link screen-reader-text" href="#content">Skip to content</a> <header id="masthead" class="site-header" role="banner"> <div class="custom-header"> <div class="custom-header-media"> <div id="wp-custom-header" class="wp-custom-header"><img src="https://contentconstantly.com/wp-content/themes/twentyseventeen/assets/images/header.jpg" width="2000" height="1200" alt="" /></div> </div> <div class="site-branding"> <div class="wrap"> <a href="https://contentconstantly.com/" class="custom-logo-link" rel="home" itemprop="url"><img width="916" height="250" src="https://i0.wp.com/contentconstantly.com/wp-content/uploads/2017/11/cropped-Logo_Transparent_PNG.png?fit=916%2C250&ssl=1" class="custom-logo" alt="" itemprop="logo" srcset="https://i0.wp.com/contentconstantly.com/wp-content/uploads/2017/11/cropped-Logo_Transparent_PNG.png?w=916&ssl=1 916w, https://i0.wp.com/contentconstantly.com/wp-content/uploads/2017/11/cropped-Logo_Transparent_PNG.png?resize=300%2C82&ssl=1 300w, https://i0.wp.com/contentconstantly.com/wp-content/uploads/2017/11/cropped-Logo_Transparent_PNG.png?resize=768%2C210&ssl=1 768w" sizes="100vw" data-attachment-id="133" data-permalink="https://contentconstantly.com/cropped-logo_transparent_png-png/" data-orig-file="https://i0.wp.com/contentconstantly.com/wp-content/uploads/2017/11/cropped-Logo_Transparent_PNG.png?fit=916%2C250&ssl=1" data-orig-size="916,250" data-comments-opened="0" data-image-meta="{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0"}" data-image-title="cropped-Logo_Transparent_PNG.png" data-image-description="<p>http://contentconstantly.com/wp-content/uploads/2017/11/cropped-Logo_Transparent_PNG.png</p> " data-medium-file="https://i0.wp.com/contentconstantly.com/wp-content/uploads/2017/11/cropped-Logo_Transparent_PNG.png?fit=300%2C82&ssl=1" data-large-file="https://i0.wp.com/contentconstantly.com/wp-content/uploads/2017/11/cropped-Logo_Transparent_PNG.png?fit=644%2C176&ssl=1" /></a> <div class="site-branding-text"> <h1 class="site-title"><a href="https://contentconstantly.com/" rel="home"></a></h1> Code (markup): Indicating they don't know enough about HTML or CSS to be building websites in the first damned place! That's how you end up with a bloated train wreck of 92k of markup to deliver 2.47k of plaintext and ZERO content images (aka not a damned thing that belongs in a IMG tag)... basically six to ten k of code's job! Idiocy like this: <article id="post-162" class="post-162 post type-post status-publish format-standard hentry category-content-marketing category-writing-content tag-content-creation tag-content-marketing"> Code (markup): ...being a poster child for everything wrong with the OOCSS mentality and incompetently coded train wrecks like turdpress. "More emphasis" on the "mental"
Of course, there are very few websites I pop into around the web that are not responsive. All of my websites I have built over the past 2-3 years are fully responsive.
The first and foremost thing is to choose a website or blog theme which is responsive. Google is going to reduce your page ranking if your site looks ugly in mobile or shorted devices. If you have not started, it is better to start it soon.