As a user, modules impose a performance hit when they contain lots of methods and classes that you don't use. If you just need a few members, you are better off creating them individually as classes instead of importing a full module.
As a browser, there is small computational overhead in initializing a module and namespace, and memory overhead in tracking, but likely not significantly different than the equivalent set of classes and class methods outside of a module.
As a writer, organizing your code into modules when you think the user will typically need all the members is good practice. Better to have a few modules with several related components (a "package") than 25 raw components or one module with all of them. This ease of use and understanding, the compartmentalization into a namespace (which lets you use meaningful names without conflicts to other namespaces), and the grouping of related classes and functions into various modules is why it is typically used in a framework, where you are likely to use most of the components for each module.